// 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.
Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.
Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.
Lists the conventions for this project and demonstrates the project scope for Claude Code skills. Use when asked about project conventions, code style, or as a demonstration of project-scoped skills.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
| title | commit-message |
| name | commit-message |
| description | 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. |
| allowed-tools | Bash(git diff *) Bash(git status *) |
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.