Conventional Commits

Default commit format: Conventional Commits. Use this format for all commits and PR/MR titles unless the project defines its own commit conventions (in CLAUDE.md, AGENTS.md, contributing guides, or similar). Project-specific rules always take priority.

When to Use

• Making any git commit -- this skill defines the required format
• Creating PR/MR titles -- squash merges use the title as the commit message
• Writing squash merge messages -- must follow the same format
• Reviewing commit message format -- validate against these rules

Critical Rules

1. Project rules override this skill -- if the project defines commit message conventions (issue number prefixes, custom formats, etc.), follow those instead. This skill is the default when no project-specific rules exist.
2. Type is required -- never commit without a type prefix
3. Description is lowercase, imperative mood, no period: fix: handle null response not Fix: Handled null response.
4. No Co-Authored-By trailer -- never add it to commit messages
5. Describe the change, not the process -- never write review provenance (fix: coderabbit round 2 fixes, fix: address review feedback) as the message; state what the commit changes. The trigger for the change already lives in the PR and its threads.
6. No filler -- the description alone is usually the whole message; add a body only for information the description and diff cannot carry (breaking change details, migration steps, non-obvious constraints). Never narrate the diff.