Commit

When to use

Use this skill when asked to commit changes, group changes into commits, or prepare commits.

Focus on why the change was made, not what changed — the diff shows the "what"
First line: imperative mood, max 72 characters (e.g. "Ensure order draft flow in unit tests")
Leave a blank line after the first line if adding a body
Body (optional): explain motivation, context, or trade-offs — not a list of files changed
Never mention AI tools, Claude, Claude Code, or assistants in commit messages
Never mention skills, slash commands, or internal tooling in commit messages
No "Co-Authored-By" lines
Be precise about what technology/component is involved — don't say "previous upgrade" or "the tool", name the specific thing (e.g., "Rails gems", "activesupport")