Write a Commit Message

A commit message is the only thing future-you will see when running git blame. The diff shows what; the message must show why. This skill produces messages that age well.

When to use

• After staging a change, before committing.
• Reviewing a PR with default-generated commit messages ("Update foo.ts").
• Squashing a stack of commits into one — write the squash message properly.

When NOT to use

• WIP/scratch commits on a feature branch that will be squashed (use wip: and move on).
• Auto-generated commits (release-please, dependabot) — let the tools handle.

The format (Conventional Commits + body)

<type>(<scope>): <subject>      ← line 1, ≤ 72 chars