Dev
Conventional Commit Message Generator
Used by developers, writers, and creators worldwide.
A Conventional Commit message generator gives you correctly formatted commit messages in the type-scope-description style that tooling can parse for changelogs and automated versioning. Choose how many you want and it returns a shuffled set — feat, fix, docs, refactor, chore, and more, each with a scope and a clear summary, including a breaking-change example with the exclamation mark. Developers use it to learn the convention, to seed example git history, and to standardise how a team writes commits. Each message follows the spec, so it works with tools like commitlint, semantic-release, and changelog generators that rely on the format. Pick the examples that match your work, copy the pattern, and write your own summary in the imperative mood. Consistent commit messages turn a git log into a readable history and let release tooling figure out the next version for you.
Read the complete guide — 4 min read
Loading usage…
Free forever — no account required
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Choose how many commit messages you want.
- Generate a set covering the types you need.
- Copy the closest pattern.
- Write your summary in the imperative mood.
Use Cases
- •Learning the Conventional Commits format
- •Standardising commit messages on a team
- •Seeding example git history for demos
- •Testing commitlint or release tooling
- •Writing a clearer, parseable git log
Tips
- →Use feat and fix to drive automatic versioning.
- →Add ! or a BREAKING CHANGE footer for major bumps.
- →Keep the summary short and in the imperative.
- →Add a scope to show what part of the code changed.
FAQ
what are the common commit types
feat and fix are core; docs, refactor, test, chore, perf, style, build, and ci cover the rest. feat and fix drive minor and patch version bumps in automated release tools.
how do i mark a breaking change
Add an exclamation mark after the type or scope, like feat(api)!: ..., or include a BREAKING CHANGE footer. Either signals a major version bump to release tooling.
why use Conventional Commits
A consistent, parseable format lets tools generate changelogs and decide the next version automatically, and it makes the git log far easier for humans to scan.
You might also like
Popular tools from other categories that share themes with this one.