Conventional Commit Message Generator

Write Conventional Commits messages: type(scope)!: subject, a body wrapped at 72 columns and a BREAKING CHANGE footer, with header length warnings.

The interactive tool loads here when JavaScript runs.

About this tool

What is the Conventional Commit Message Generator?

The Conventional Commit Message Generator builds a git commit message from a short form. Choose the change type (feat, fix, docs, style, refactor, test, chore, perf, ci, build or revert), describe the change, list the files you touched, and optionally describe the bug and root cause, the testing you did and any notes. You get a header, a body and the full message, each with its own copy button.

The header follows Conventional Commits 1.0.0: type(scope): subject, with ! added after the scope for a breaking change. The scope comes from the first file you list (src/auth/login.ts gives auth); a file in the repository root gives no scope rather than an invented one. The subject is kept on one line and loses its trailing period, the body is wrapped at 72 columns, and a breaking change gets a proper BREAKING CHANGE: footer.

You get a warning when the header runs past 72 characters. Everything runs in your browser.

  • Conventional Commits 1.0.0 headers with optional scope and !
  • BREAKING CHANGE footer
  • Body wrapped at 72 columns with hanging indents for lists
  • Header length warnings
  • Separate copy buttons for title, body and full message
Read the guide: Conventional Commits and the 50/72 Rule, Explained

Updated

How to use the Conventional Commit Message Generator

  1. Pick a Change Type and write the Change Description in the imperative ("add retry to webhook sender").
  2. List Files Changed separated by commas; the first one sets the scope.
  3. For a fix, describe the bug and root cause. Tick the kinds of testing done and add details.
  4. Tick "This is a breaking change" and explain what callers must change in Additional Notes.
  5. Press Generate Commit Message and copy the title, the description or the full message.

Worked examples

A breaking change

Input

Type feat, description "drop Node 16 support", files package.json, breaking, notes "Node 18 or newer is now required."

Output

feat!: drop Node 16 support

Files changed:
- package.json

BREAKING CHANGE: Node 18 or newer is now required.

package.json sits in the repository root, so there is no scope. The ! in the header and the footer both signal a major version bump.

The loaded sample

Input

Type fix, first file src/auth/SessionManager.js, with bug, root cause and testing filled in

Output

fix(auth): Fixed memory leak in user session management

Problem: User sessions were not being properly cleaned up after logout,
causing memory consumption to grow over time
...

Body lines are wrapped at 72 columns. Many teams would also rewrite the subject in the imperative: "fix memory leak in session management".

Background and insight

Conventional Commits grew out of the Angular project's commit guidelines and was published as a standalone specification; version 1.0.0 is the current one. Its value is that machines can read it. fix maps to a SemVer patch release, feat to a minor release, and a ! or BREAKING CHANGE footer to a major release, which is what tools like semantic-release, release-please and standard-version rely on to bump versions and write changelogs.

The 50/72 habit is older than the spec. Tim Pope's 2008 note on commit messages recommended a summary of about 50 characters and a body wrapped at 72, so that git log, git format-patch emails and terminal tools stay readable. One more git detail matters for generated messages: when you edit a message in your editor, git removes lines that start with #, so this tool uses plain "Problem:" and "Root cause:" labels instead of Markdown headings.

Common use cases

  • Adopting Conventional Commits

    Learn the header format and footers while your team sets up commitlint or a release tool.

  • Writing a careful fix commit

    Record the problem, root cause and testing so the next person running git blame understands the change.

  • Announcing a breaking change

    Produce a correct BREAKING CHANGE footer that release tooling turns into a major version and a changelog entry.

  • Squash-merge messages

    Write a clean summary message for a pull request that will be squashed into one commit.

Tips and limitations

  • Write the subject in the imperative mood, as if completing "If applied, this commit will...".
  • Keep the header under 72 characters; 50 is the classic target and fits git log --oneline on narrow terminals.
  • Multi-line messages do not fit neatly in git commit -m. Save the message to a file and run git commit -F msg.txt, or paste it into the editor git opens.
  • Reference issues with a footer such as Refs: #123 or Closes #123; the generator does not add placeholder issue numbers.
  • Scope is optional in the spec. If the first file gives the wrong scope, reorder the file list or edit the header.

Sources and further reading

  1. Conventional Commits 1.0.0, Conventional Commits. The specification, types and BREAKING CHANGE footer
  2. Semantic Versioning 2.0.0, Semantic Versioning. How fix, feat and breaking changes map to version numbers
  3. A Note About Git Commit Messages, Tim Pope. The 2008 note behind the 50/72 convention
  4. git-commit Documentation, Git. Commit message cleanup and comment lines starting with #

Frequently asked questions

What is the Conventional Commits format?

A header of type(scope): description, an optional body after a blank line, and optional footers such as BREAKING CHANGE: or Refs:. The type says what kind of change it is, feat and fix being the two the spec defines, and the scope names the affected area.

How do I mark a breaking change in a conventional commit?

Add ! after the type or scope, as in feat(api)!: remove v1 endpoints, and add a footer starting with BREAKING CHANGE: that explains what users must change. Either one signals a major version bump to release tools; using both is clearest.

Why wrap commit message bodies at 72 characters?

Git does not wrap text for you, and git log indents the body by four spaces. Wrapping at 72 keeps lines under 80 columns in terminals and in patch emails. Most editors with a git commit mode wrap at 72 automatically.

What is the difference between chore, build and ci commits?

build covers the build system and dependencies, such as package.json or webpack config. ci covers CI configuration like GitHub Actions workflows. chore is for maintenance that touches neither source nor tests. Only feat and fix are defined by the spec; the rest come from the Angular convention.

Why does this commit message tool not use Markdown headings?

Because git treats lines starting with # as comments and removes them when you edit the message in an editor. Plain labels such as "Problem:" and "Root cause:" survive every git workflow and still read well on GitHub.

Is there an in-depth guide to the Conventional Commit Message Generator?

Yes. “Conventional Commits and the 50/72 Rule, Explained” covers the background, how it works, common pitfalls and worked examples. Read the full guide.