Git Commit Messages

Use this skill to create commit messages that make project history useful to future readers. Treat the diff as the record of what changed; use the message to explain the change's intent, context, and consequences.

Primary source: Chris Beams, "How to Write a Git Commit Message": https://cbea.ms/git-commit/

Drafting Workflow

1. Inspect the change or user-provided summary.
2. Identify the single main intent of the commit.
3. Draft a concise subject line.
4. Add a body only when it provides context that the subject and diff cannot.
5. Review the result against the rules below.

If the change cannot be summarized as one coherent intent, recommend splitting it into separate commits before polishing the message.