Last verified
Commit Helper Plugin
VerifiedGenerate Conventional Commits messages from staged diffs with one command
Add marketplace
/plugin marketplace add anthropics/claude-plugins-officialCommands
- /commit
- /commit-amend
Hooks
- pre-commit
"Three months in, every commit in our repo is machine-readable. The CHANGELOG writes itself."
What is the Commit Helper Plugin?
The Commit Helper Plugin is an official Claude Code plugin that generates commit messages for developer tools workflows. It reads staged git changes, infers the change type, scope, and intent, and writes a Conventional Commits-compliant message for you to review and confirm before git commits.
How does it work?
After installing from the official marketplace, run /commit with staged changes. The plugin calls git diff --cached, sends the output to Claude with a structured prompt, and returns a formatted message. Edit it in-terminal before accepting, or accept as-is. The optional pre-commit hook fires automatically every time you run git commit, surfacing the generated message before git opens the editor.
Commit Helper pairs well with the Code Review plugin: run /review to catch issues, fix them, then run /commit to describe what changed.
When should you use it?
Use the Commit Helper plugin in any project where a readable git history matters: open source libraries, team codebases, or long-lived products where git bisect and git log are regular tools. It’s particularly worth having on large refactors where the diff is obvious but finding the right description is slow.
Frequently asked questions
Does Commit Helper enforce Conventional Commits format?
Yes. It outputs a message in the `type(scope): description` pattern, with type drawn from the standard set: feat, fix, docs, style, refactor, test, chore. You can override the type or scope before confirming and add a body or breaking-change footer if the change warrants it.
What happens if the diff is too large for a single commit message?
Commit Helper spots diffs that span multiple logical changes and suggests splitting them. It describes each logical unit separately and recommends which files to stage for each commit, so the git history stays clean and bisect-friendly.
Can I configure the plugin to use a custom commit format instead of Conventional Commits?
Yes. Add a `commit_format` key to `.claude/commit-helper-config.json` with a template string. The plugin uses your template while still inferring the type, scope, and description from the diff.