Agent skill · software engineering · aiskillstore
commit-message
Format git commit messages combining Conventional Commits summary lines with Linux kernel-style bodies. Use when writing, reviewing, or formatting commit messages.
Why this skill is useful
Codifies a specific commit message format that the AI could infer but now doesn't have to guess.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Commit Message Formatting Summary Line Use Conventional Commits format: type (required): feat, fix, docs, style, refactor, perf, test, build, ci, chore scope (optional): component or area affected, in parentheses description: imperative mood, lowercase start, no period, max 50 chars (hard limit 72) For breaking changes: add ! before colon: feat(api)!: remove deprecated endpoint Body Separate from summary with blank line. Follow kernel style: Wrap at 72 columns Imperative mood ("Add feature" not "Added feature") Explain why, not what (the diff shows what) Describe user-visible impact and motivation Quantify improvements with numbers when applicable When referencing commits, use 12+ char SHA with summary: No Trailers Omit all trailers: no Signed-off-by, Reviewed-by, Acked-by, Tested-by, Cc, Fixes, Link, etc. Examples Single-line fix: Feature with body: Breaking change: Refactor:
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/commit-message