git-commit-convention
Installation
SKILL.md
Conventional Commits 1.0.0 defines a human-readable and machine-parseable commit message format. Before writing a message, plan the commit boundary from the complete change set; a multi-round conversation may produce several coherent commits rather than one catch-all commit. In the spec, feat implies MINOR, fix implies PATCH, and breaking changes imply MAJOR; other type-to-version mappings are project conventions.
- Only
typeanddescriptionare required; everything else is optional - Scope narrows the affected area:
feat(auth):,fix(api): - Breaking changes use
!suffix orBREAKING CHANGE:footer (or both) - Footer tokens follow Git trailer convention
- Default to English, but match the project's existing convention — check
git logand follow whatever language recent commits use - Decide commit boundaries from purpose and dependency, not from the number of conversation rounds
- Validate each message against the staged diff: every staged change must belong to the stated purpose, and every material claim must be supported by the diff
- When asked to commit, state the proposed commit plan before creating any commit; then validate each staged commit separately
<type>[optional scope][!]: <description>
[optional body]
[optional footer(s)]