Skill Finder
The best Claude skills for Git and pull requests
Start with git-commit from GitHub: it has the top main score here, 81, needs only Git, and turns your working changes into Conventional Commits, one logical change per commit, without pushing. The list also covers gh-issue-sync for GitHub issues as local Markdown files, and secondary picks for terse commit messages, staged pull request work, Linear tickets and reviews in CI.
The 2 skills made for this job
-
1
Get git-commitgit-commit
For developers who want Claude to stage and commit changes with Conventional Commits messages. Skip it if you only want a message drafted, or need pushes and rebases.
-
2
Get gh-issue-syncgh-issue-sync
For developers who want to triage and edit GitHub issues as local Markdown files. Skip it if your team tracks work in Jira, Linear or a tool other than GitHub Issues.
Also useful for git
Their main job is something else, but they help with this one.
-
Get CavemanCaveman
For developers who want terse commit messages, one-line review comments and lower token spend. Skip it if you prefer full, explanatory prose from Claude.
-
Get orca-linearorca-linear
For Orca users who want Claude to update, search and close out Linear tickets from the terminal. Skip it if you do not run Orca or track work in Linear.
-
Get Compound EngineeringCompound Engineering
For developers who want Claude to plan, build, review and ship work in fixed stages with saved plans. Skip it if you prefer quick ad hoc edits without a process.
-
Get review-prreview-pr
For teams running automated PR reviews in CI who want structured JSON output instead of direct GitHub posts. Skip it if you want Claude to comment on a PR by hand.
How to choose
git-commit reads your commit rules from a commitlint config, CONTRIBUTING.md and the last ten log messages, then stages one change per commit. It checks staged files for secrets such as .env files and writes a 72-character summary line at most. It never pushes or rebases unless you ask.
gh-issue-sync mirrors GitHub issues as Markdown files in .issues/open/ and .issues/closed/. Claude pulls, edits the files, checks the diff and pushes changes back, and a .comment.md file beside an issue posts as a comment. It needs the gh-issue-sync tool and a repository on GitHub.
The other four are secondary picks. Caveman's caveman-commit writes a short commit message and prints it without committing. Compound Engineering includes ce-commit-push-pr and ce-babysit-pr in its staged workflow. review-pr from Warp writes review.json for CI, and at least one scanner rated orca-linear high risk.