Skip to main content
Back to Dev generators

Dev

Conventional Commit Generator

Used by developers, writers, and creators worldwide.

A Conventional Commit generator builds a commit message in the Conventional Commits format, the standard that powers automated versioning and changelog tools. Pick a type — feat, fix, docs, refactor, and so on — add an optional scope, and write a short description, and it returns a correctly structured subject line plus commented prompts for the body and footer. Teams use it to keep commit history consistent and machine-readable, so tools can determine version bumps and generate release notes automatically. The type and optional scope are formatted exactly as the spec expects, and the description is lower-cased to match convention. Everything runs in your browser. Copy the subject line for your commit, and fill in the body and footer when a change needs more explanation or references an issue. Consistent commit messages make a project's history easier to read and unlock automation that depends on the format.

Loading usage…

Free forever — no account required

How to use

  1. Choose your options above
  2. Click Generate
  3. Copy your result

Detailed instructions

  1. Select the commit type.
  2. Add an optional scope and a short description.
  3. Click Generate to build the commit message.
  4. 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 conventional commits

Conventional Commits is a specification for commit messages with a structured subject line — type(scope): description — and optional body and footer. Tools read this format to decide semantic version bumps and to generate changelogs automatically.

what do the types mean

feat adds a feature, fix patches a bug, docs changes documentation, style is formatting only, refactor restructures without behaviour change, perf improves performance, test adds tests, and chore covers maintenance. Pick the one that best describes your change.

how do i flag a breaking change

Add a footer line beginning with "BREAKING CHANGE:" followed by an explanation, or append an exclamation mark after the type or scope. This signals tools to bump the major version, alerting users that an upgrade may require code changes.