How do I generate a Conventional Commits message from a diff?

Paste git diff or git show output, optionally set a scope hint, choose Conventional Commits style, and copy the generated subject and body.

Will the commit message invent files I did not change?

It should stick to the pasted patch. Always skim the message before committing.

Is my git diff stored?

No. Generation runs on Codeground’s self-hosted AI without persistence. Still scrub secrets from the diff before pasting.

Can I use the output as a pull request description?

The body is a solid starting PR summary. Add your own test plan and screenshots as needed.

Git

Commit Message from Diff

Paste a unified diff and get a Conventional Commits message with subject + body — ready to paste into git or a PR.

Privacy: Runs on Codeground's self-hosted AI. Your diff is not stored.

AI can make mistakes. Please review important output before you rely on it.

Paste unified diff

Style

Scope hint (optional)

476 / 24000 chars

Better commits from the actual patch

Prefer git diff / git show output over guessing from memory. This generator reads the unified diff and drafts a Conventional Commits subject (and optional body) that matches what actually changed — ideal after AI coding sessions where you touched many files and need a clean history.

Conventional Commits cheat sheet

feat: new user-facing capability
fix: bug fix
refactor: no behavior change intended
perf / test / docs / build / ci / chore: scoped maintenance work
Optional scope in parentheses: feat(auth): …

How to generate a commit message

Run git diff (or git diff --cached) and paste the output.
Optionally set a scope hint (auth, api, ui).
Choose Conventional Commits or a simple subject + body style.
Copy the message into git commit or your PR description.

Commit message generator FAQ

Will it invent files I did not change? It should not — the model is instructed to stick to the patch. Always skim the message before committing.

Secrets in the diff? Scrub them first. Anything you paste is processed by our self-hosted model and is not stored, but you still should not leak credentials.

Huge diffs? Stay under the character limit. Split into logical commits when possible — better history and better messages.

PR descriptions? The body often works as a starting PR summary; expand with test plan notes yourself.