Total 50,394 skills, Version Control has 883 skills
Showing 12 of 883 skills
Create well-formatted commits with conventional commit format.
Move completed local GitHub issue work to a ready-for-merge pull request. Use when development is complete, the user says finish PR, publish this branch, open a ready PR, or an agent has objective evidence the branch is ready for review.
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
This skill should be used when a developer wants to open a pull request for a completed task branch — for example "create a PR", "open a pull request", "submit this for review", "make a PR for task
设置 Claude Code hooks，在危险 git commands（push, reset --hard, clean, branch -D 等）执行前阻止它们。Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
Generates properly formatted Git branch names following project conventions. Use this skill whenever the user wants to name a branch, create a branch, or asks things like "what should I call this branch?", "what branch name should I use?", "help me with the branch name", or describes a feature/fix and needs a branch name. Always use this skill when the user needs a git branch name, even if they don't explicitly say "branch".
Turn many commits into a curated grouped squash summary compatible with the opinionated wording style of git-visual-commits. Use this skill whenever the user asks to squash a branch into a concise summary, write a squash-and-merge summary, summarize a commit range or PR as grouped lines, clean up noisy commit history, or asks for a curated summary without committing. Treat phrases like "squash summary", "squash commit message", "summarize this branch", "turn these commits into one summary", "rewrite these 10+ commits", or "draft the squash summary" as automatic triggers. This skill is non-mutating: it inspects git history and diffs, then returns grouped summary lines only. It preserves technical identifiers where possible, groups by intent rather than chronology, merges overlapping commits, drops low-signal noise, uses strong concrete verbs, favors readable GitHub and terminal output, keeps every output line at or below 72 characters, and does not invent unsupported changes or drift into changelog wording.
GitHub operations expert for PRs, issues, code review, Actions, and gh CLI
Record git activity summary in memory log.
Create a feature branch in a Git worktree, work independently, then merge back and clean up safely.
Git and GitHub wizard using gh CLI for all git operations and GitHub interactions
Addresses all PR review comments, resolves merge conflicts, and fixes failing CI checks to get the PR ready to merge. Use when the user wants to make their PR "all green" or ready for merge.