Commit Message Builder

Write a clear Conventional Commit message in seconds.

Private by design

Your inputs stay on your device and are not sent to our servers. Optional usage analytics does not receive your files or tool inputs.

Commit Message Builder

Conventional Commits with scope, breaking changes and issue links

Description, then optional body

Commit message

The result appears here.

Options

Type

Scope (optional)

Breaking change

Issue linksComma separated: #12 or owner/repo#12.

Link keyword

Wrap the body at 72 characters

A Conventional Commit looks like type(scope): description, then an optional body and footers. The shared format lets tools build changelogs and choose version numbers automatically. A ! after the type, or a BREAKING CHANGE footer, marks a change that breaks existing users.

Keep the first line short and in the imperative: add, fix, remove.
Use the body to explain why, not just what.
Closes #12 in a footer lets GitHub close the issue when the commit lands.

Follows the Conventional Commits 1.0.0 specification (conventionalcommits.org): header, blank line, body, blank line, footers; breaking changes marked with ! and a BREAKING CHANGE footer. Types are the common Angular set. Runs entirely in your browser.

Preparing tool

How to use Commit Message Builder

Write the description on the first line and an optional body below it.
Choose the type and scope, mark breaking changes and add issue numbers.
Copy the message and use it with git commit.

Read the detailed guide →

What are the limits of Commit Message Builder?

Follows Conventional Commits 1.0.0 and the common Angular types. It checks style but cannot judge whether the message is accurate. Your data stays on your device.