Dev
Conventional Commit Message Generator
Teams without commit conventions end up with logs full of "fix stuff" and "wip", which are useless for generating changelogs or deciding the next version. This tool returns a shuffled set of Conventional Commits messages in the correct `type(scope): description` format. The only input is how many you want, from 1 to 10 (14 in the pool). The set covers all standard types — `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, `perf`, `style`, `build`, `ci`, `revert` — each with a specific scope and clear summary. One message, `feat(api)!: drop support for v1 endpoints`, demonstrates the breaking-change `!` notation that triggers a major version bump in release tooling. Copy the closest pattern and write your own description in the imperative mood.
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 commit types are in the pool
The pool includes `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, `perf`, `style`, `build`, `ci`, and `revert`. `feat` and `fix` are most important because automated release tools map them to minor and patch version bumps respectively.
how do I signal a breaking change
Add `!` after the type or scope — like `feat(api)!:` — or include a `BREAKING CHANGE:` footer in the commit body. Either form signals a major version bump to `semantic-release` and similar tools. The pool includes one `!` example.
why use Conventional Commits over free-form messages
A machine-parseable format lets tools generate changelogs and determine the next semantic version automatically. It also makes the git log readable at a glance — `fix(auth): prevent token reuse after logout` tells you the what and why without opening the diff.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.