Dev
Conventional Commit Generator
Commit messages like "fix stuff" make history unreadable and break the changelog and versioning tools that depend on a consistent format. The Conventional Commits specification solves this with a structured subject line tooling can parse — this generator builds that line for you. Three inputs shape the output: the Type dropdown (feat, fix, docs, style, refactor, perf, test, chore), an optional Scope for a parenthesised component name, and a Description that is lower-cased to match the convention. The output is the formatted subject line plus commented prompts for the optional body and footer. Copy the subject line for your commit. Use the body to explain what changed and why. Add a BREAKING CHANGE: footer to trigger a major version bump, or Closes #123 to link an issue. Teams using this format with semantic-release get automated versioning from commit history.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Select the commit type.
- Add an optional scope and a short description.
- Click Generate to build the commit message.
- Copy the subject line and fill in the body or footer if needed.
Use Cases
- •Writing commit messages that follow Conventional Commits
- •Keeping commit history consistent across a team
- •Enabling automated versioning and changelog tools
- •Learning the Conventional Commits format
- •Standardising how scopes and types are written
Tips
- →Keep the description short, imperative, and lower-case.
- →Use a scope to indicate the part of the codebase affected.
- →Add a BREAKING CHANGE footer to trigger a major version bump.
- →Reference issues in the footer with "Closes #123".
FAQ
what are the supported commit types and what do they mean
feat adds a user-facing feature, fix patches a bug, docs changes documentation only, style is formatting with no logic change, refactor restructures without changing behaviour, perf improves performance, test adds or updates tests, and chore covers maintenance tasks like dependency updates.
how do I signal a breaking change
Add a footer line starting with "BREAKING CHANGE:" followed by a description. Some tooling also accepts an exclamation mark after the type or scope — feat!: — but the footer is the canonical approach in the specification.
what happens to the scope and description inputs
The scope is cleaned to alphanumeric characters, hyphens, and underscores, then wrapped in parentheses. If empty it is omitted. The description has its first character lower-cased. Both are joined into the type(scope): description format.
what tools consume conventional commit messages
semantic-release, standard-version, conventional-changelog, and Release Please read conventional commit history to determine version bumps and generate changelogs automatically. The messages this generator produces are compatible with all of them.
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.