Commit Message Builder
Build clean Conventional Commits messages with live preview, scope, breaking-change flags, footers, and gitmoji. Copy-ready output, deep-link share, and recent history.
Cheatsheet · Conventional Commits types
About this tool
A Conventional Commits message builder that helps you write structured, machine-readable commit messages. Pick a type (feat, fix, docs, refactor, …), add an optional scope, write a short imperative summary, and the tool assembles the correctly formatted line with a live preview you can copy straight into your terminal.
Example: type feat, scope auth, summary "add OAuth login" produces feat(auth): add OAuth login. Add a breaking-change footer and the output becomes feat(auth)!: add OAuth login with a BREAKING CHANGE: footer, which tools like semantic-release use to auto-bump the major version.
Handy for teams that auto-generate changelogs, anyone learning the Conventional Commits spec, or when you want a gitmoji prefix without memorizing the emoji shortcodes.
FAQ
What is a Conventional Commit? ›
A commit message format defined at conventionalcommits.org: <type>(scope): description. The structured prefix lets tooling parse history and automatically derive semantic version bumps and changelogs.
What does the "!" after the scope mean? ›
An exclamation mark right before the colon (e.g. feat(api)!: ...) marks a breaking change. Release tools treat it as a signal to increment the major version number.
What are gitmoji and should I use them? ›
Gitmoji are emoji prefixes for commits (e.g. ✨ for feat, 🐛 for fix). They are optional and purely visual; enable the toggle if your project uses them.