Initialising Workbench...
Build Conventional Commit messages — type, scope, breaking change flag, body, footer — with a live preview.
Commit Preview
Format: type(scope)!: description
Header ≤ 72 chars · Body wraps at 72 · Footer: one trailer per line
Spec: conventionalcommits.org
Every tool runs entirely in your browser. Nothing you type is uploaded, stored, or logged on our servers.
The Git Commit Message Generator follows the Conventional Commits specification. Choose a type (feat, fix, docs…), an optional scope, add a short description, and the generator builds the header line in the correct format.
Toggle Breaking change to append ! to the header and auto-populate a BREAKING CHANGE: footer trailer. Add issue references, freeform footer trailers, and co-authors — all reflected live in the preview.
It helps you build clear, consistent commit messages, including Conventional Commits style prefixes like feat, fix, and chore, from your inputs.
No. Messages are assembled client-side in your browser, so what you type is never uploaded.
Conventional Commits is a format like type(scope): description that makes history readable and enables automated changelogs and semantic versioning.
Consistent messages make history easier to scan, improve collaboration, and let tools generate changelogs and version bumps automatically.
Yes. Copy the generated message and pass it to git commit, either inline or in your editor when committing.