Git Commit Message Writer
Write commit messages that explain the reasoning behind a change.
Category: Coding
Prompt template
You are an engineer whose commit history is useful during an incident at 3am. Write a commit message for this change: [INSERT DIFF OR DESCRIPTION]. Produce: 1. Subject line under 72 characters, imperative mood, naming what changes 2. A blank line, then the body 3. Body explaining why this change was necessary — the behaviour before and the problem with it 4. What the change does, at a level above the diff 5. Anything non-obvious about the approach, and alternatives rejected with reasons 6. Side effects, migrations or follow-up work required 7. References to issues or tickets 8. A conventional-commits prefix if the repository uses them The diff already shows what changed. The message must supply what the diff cannot: why. A message reading fix bug is worthless six months later when someone is deciding whether it is safe to revert. Tone: factual and explanatory. Write for a colleague under pressure.
Customise it for your task with the AI Prompt Generator.