Commit message from diff
AIPaste a unified diff or describe what changed. You'll get a suggested commit title (and optional body) in Conventional Commits style. Review and edit before committing—never paste API keys or tokens.
Diff or summary
?
Common use cases
- Draft a Conventional Commits-style title when the diff is clear but wording is slow.
- Brainstorm bodies for larger changes before trimming to team norms.
- Unblock a merge request when reviewers ask for clearer history.
Common mistakes to avoid
Pasting diffs that contain credentials or internal URLs
Redact secrets, keys, and customer data. Assume remote processing when server-assisted mode is on.
Committing generated text without reading it
You are responsible for the final message; edit tone, scope, and breaking-change notes to match reality.
FAQ
Does this run git commands for me?
No. It only suggests text—you run git commit locally with the message you approve.
Will the message match my team’s convention?
It aims at common Conventional Commits patterns. Adjust prefixes, scopes, and footers to your policy.
More tools
Related utilities you can open in another tab—mostly client-side.
Plain text diff
ClientCompare two text drafts side by side—unified view, sample pre-filled, client-side.
Tone rewriter
AIRewrite English in formal, casual, shorter, or bullet-list style—redact secrets before pasting.
JSON & error explainer
AIPaste a parse error or bad JSON; get causes and fix hints—redact secrets; validate in the JSON formatter.
Shell command explainer
AIPaste a Bash-style command; get flags and risks explained—nothing is executed on the server.