Commit Message

Produce a Conventional Commit message (type(scope): description) anchored in the real git diff, surface breaking changes, obtain explicit user approval, then run git commit. Six rule cards across five categories enforce header format, safety, grounding, procedure, and style.

When to Apply

Reference these guidelines when:

• Drafting, writing, or generating a commit message from a real git diff
• Amending an existing commit or converting a rough plan into a Conventional Commit
• Mentioning Conventional Commits, BREAKING CHANGE footers, or type(scope) headers
• Running git commit after a human review of the proposed message

When NOT to Apply