Checked live against Conventional Commits: type(scope)!: description where type is one of feat, fix, docs, refactor, perf, test or chore. A generated title lands here and stays editable.
Nothing to paste? — a five-file branch that adds retry backoff to a job queue. Or , rendered from a saved reply with no run and no charge.
Paste the diff
The scan runs in your browser: files changed, insertions and deletions, and a split across core code, tests, generated files, docs and config. Those numbers go to the model, so it never has to guess at LOC.
Add the why
Commit subjects and your own notes carry the motivation the diff cannot. Leave them out and the description says the motivation was not stated rather than inventing one.
Paste it into GitHub
A Conventional Commits title and a description that leads with the goal, then the shape of the solution, then the trade-offs — with a ticked change type, a real test plan, and release notes when there is anything user-facing.