LLM prompt for writing commit messages

Paste a diff, get a commit message that follows the conventions and says why, not just what.

SNP 091 #35B Filed llm prompt git

Pipe the staged diff into your tool of choice with this:

markdown
Write a git commit message for the diff below.

RULES
- Conventional Commits: type(scope): summary. Types: feat, fix, refactor, perf, docs, test, chore, build, ci.
- Summary line: imperative mood, no trailing period, at most 72 characters.
- Then a blank line and a body that explains WHY the change was made and anything a reviewer would not guess from the diff. Wrap at 72 characters. Skip the body when the summary says everything.
- Mention breaking changes in a "BREAKING CHANGE:" footer.
- Do not list the files changed. Do not invent a reason that isn't in the diff; if the intent is unclear, say so in one line and ask.
- Output only the commit message, no quotes, no commentary.

DIFF
<paste the output of `git diff --staged` here>

Read the message before you commit it. The model guesses the intent; it doesn't know it.