Commit Message Generator
Paste a git diff, get a clear commit message — Conventional Commits or plain, your choice.
Why bother generating commit messages?
A commit history is documentation nobody has to write separately — but only if the messages actually describe what changed and why. Pasting the raw diff in lets the model describe the actual code change instead of guessing from a vague memory of what you were doing, which is the usual failure mode of commit messages written after the fact.
Frequently asked questions
What's the difference between the two formats?
Conventional Commits prefixes the summary with a type like feat, fix, or refactor — useful if your repo uses it for changelogs or semantic versioning. Plain is just a clear imperative summary line with no prefix convention.
Does it work with git diff --staged?
Yes — paste the output of either `git diff` or `git diff --staged`, whichever reflects the change you want a message for.
Will it make up context that isn't in the diff?
It's instructed not to. If the diff alone doesn't make the motivation clear, it describes the mechanical change rather than guessing why you made it — you may still want to add that context yourself.
Is my code stored?
No. The diff is sent to generate the message and is not stored afterward.