Commit Commands Plugin: /commit and /commit-push-pr
commit-commands is Anthropic's Claude Code plugin with /commit, /commit-push-pr and /clean_gone for git commits, pull requests and stale branch cleanup.
By Claudekit Team Published 1 min read
- Type
- Plugin
- Pricing
- Open Source
- Repository
- github.com
- Website
- github.com
commit-commands is an Anthropic plugin with three slash commands for everyday git work in Claude Code. It drafts commit messages from your changes, takes a branch all the way to an open pull request, and cleans up local branches that were deleted on the remote.
Checked 24 Oct 2026 against the plugin’s README and marketplace.json.
Who it is for
Anyone who commits often from inside Claude Code and wants fewer manual git steps.
Install
/plugin install commit-commands@claude-plugins-officialWhat it does
- /commit: reviews staged and unstaged changes, drafts a message in your repo’s style, stages relevant files and commits.
- /commit-push-pr: creates a branch if you are on main, commits, pushes to origin and opens a PR with a summary and test plan. It returns the PR URL.
- /clean_gone: finds local branches marked
[gone], removes their worktrees and deletes them.
Use cases
- Commit a working step without leaving the session.
- Turn a finished feature branch into a PR in one command.
- Tidy your branch list after a batch of merges.
Pros
- Small and predictable; each command does one job.
- Commit messages follow your existing history.
- Skips obvious secret files.
Cons and caveats
- Commits and PR bodies include Claude Code attribution by default.
- PR creation needs
ghand GitHub. - Always read the drafted message; it describes what changed, not why you changed it.
Links
- Plugin folder: plugins/commit-commands
- Related: slash commands guide, Code Review plugin, Claude Plugins Official
Frequently asked questions
Does /commit match my commit style?
Yes. It reads recent commit messages to match your repository's style before drafting a message, and avoids committing files like .env or credentials.json.
What does /commit-push-pr need?
The GitHub CLI installed and authenticated, and a remote named origin. It creates a branch if you are on main, pushes, and opens the PR with gh pr create.
Is /clean_gone safe?
It only deletes local branches marked [gone], meaning already deleted on the remote, and removes their worktrees first. Run git fetch --prune so branches show as gone.