Total 50,396 skills, Version Control has 883 skills
Showing 12 of 883 skills
Local branch cleanup after PR merge: identify, switch, delete, prune in 4 steps. Use when a PR has been merged and local branches need cleanup, when stale branches accumulate, or when user says "clean up branches", "delete merged branch", or "prune". Do NOT use for branch creation, PR review, or CI checks.
Smart git commit workflow using Conventional Commits format with AI-generated commit message suggestions based on staged changes.
Push the current branch to origin safely (lint, test, resolve non-fast-forward via pull skill, then push). Use when the user asks to push or publish commits to the remote. Does not create or edit PRs—use the create-pr-jp skill for that.
Merge the latest default branch (e.g. origin/main) into the current branch, resolve merge conflicts, and verify with pnpm lint && pnpm test. Merge-based sync (not rebase) unless the repo specifies otherwise. Use when syncing a feature branch with origin, after a non-fast-forward push, or when the branch is behind. Does not push or manage PRs—use push and create-pr-jp for those.
Manages semantic versioning releases — version bumps, changelogs, tags, publishing. Use when preparing a new release.
Use this skill when addressing, responding to, or resolving PR review comments on GitHub pull requests. Triggers on "address PR comments", "respond to review", "handle review feedback", "reply to PR comments", "fix review comments", or when the user wants to process open review threads on their PR. Uses the gh CLI to fetch unresolved comments, make code changes where agreed, and post batch replies with a humble, thankful tone.
Keep AI tooling files (.claude, .codex, .cursor, .windsurf, .augment, .kiro, .cline, .roo, .gemini, etc.) on dev branch but exclude them from main/master. Use when managing branches, creating PRs to main, merging to main, or setting up a repo's branch strategy for AI-assisted development. Triggers on git merge/PR operations targeting main or master.
This is used to review comments on an active pull request and decide whether to accept, iterate, or reject the changes suggested in each comment.
Git Worktrees enables parallel development by maintaining multiple checked-out branches simultaneously in separate directories.
Use when needing multiple checked-out branches simultaneously without re-cloning — review a PR while keeping WIP, per-branch build caches, or hotfix alongside feature work
Analyses git changed files in the workspace and makes atomic, functional, and semantic commits using conventional commits format. Use when the user asks to commit changes, create commits from staged/unstaged files, or organise working tree changes into meaningful commits.
Correct naming for a PR