Paste the output of git diff and get a commit message that actually explains the change: a concise subject line under 72 characters plus a body covering what changed and why. Supports Conventional Commits if your repo uses that format.
Output of `git diff --staged` works best.
Your result will appear here.
A convention where messages start with a type such as feat, fix, docs, or refactor, followed by an optional scope. It makes history easy to scan and enables automated changelog and version tooling.
A diff already shows what changed. The message should capture intent, which is the part future readers can't reconstruct from code alone. Edit the generated body to add context the diff can't show.
It works best on a single focused change. Large mixed diffs usually mean the work should be split into separate commits anyway.