Generate a conventional commit message for the current staged git changes. Use when the user wants to commit, asks for a commit message, or asks what to write for a commit.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Run git diff --staged to see exactly what is staged for the next commit.
Run git status --short to understand the full scope of changes (staged and unstaged) and identify the files involved.
If nothing is staged, tell the user there is nothing staged and suggest they run git add first. Stop here.
Choose the correct Conventional Commits type based on the diff:
feat: a new feature or capability visible to users or callersfix: a bug fixdocs: documentation changes onlystyle: formatting, whitespace, missing semicolons — no logic changerefactor: code restructuring with no behavior change and no new featuretest: adding or correcting testschore: build system, dependency updates, tooling, CI configDetermine the scope from the changed files. The scope is optional but useful when the change is clearly isolated to one module, package, or layer (for example, api, auth, db, cli). Omit it if the change is broad.
Write the subject line:
type(scope): description or type: description if no scopeIf the diff is non-trivial (more than one logical change, or a change whose motivation is not obvious from the code), add a body:
Output only the commit message text. No surrounding explanation, no markdown code block wrapping.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
The English summary is being prepared. Showing the original description.
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
The English summary is being prepared. Showing the original description.
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
The English summary is being prepared. Showing the original description.
Create a git branch named after a GitHub issue.
The English summary is being prepared. Showing the original description.
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.