Skip to content
M2TOOLKIT

Developer · free tool

Commit Message Generator

Write consistent, useful git commit messages.

Use it as often as you like — it's free, with no sign-up and no limits.

  • Developer
  • Free
  • No sign-up
  • Runs in your browser
  • Updated
Type of change

First line: 6 / 72 characters

Write a short subject describing the change.

Commit from the terminal

git commit -m "feat: "

Everything you type is processed in your browser. Nothing you enter is sent to our servers or stored by us.

How to use the Commit Message Generator

  1. Choose the type of change and an optional scope.
  2. Write a short imperative subject and, if needed, a body.
  3. Copy the message — or the full git commit command.

What does this tool do?

Conventional Commits (feat:, fix:, docs: …) make history easy to scan and let tools generate changelogs and version numbers automatically. The generator keeps the first line short, wraps the body at 72 characters, adds BREAKING CHANGE footers and warns about past-tense subjects.

Everything runs in your browser — nothing you paste is uploaded.

Why use it?

  • Spec-compliant format.
  • Length checks.
  • Optional gitmoji.

Use cases

  • Keep git history readable on team projects.
  • Generate changelogs and version bumps automatically.
  • Learn the Conventional Commits format.

A good conventional commit

feat(auth): add password reset by email

Users can request a reset link from the login page. Links expire after 30 minutes.

Closes #142

Common mistakes

  • Past tense subjects (“added”) — use the imperative (“add”).
  • Subject lines over about 50–72 characters.
  • Bundling unrelated changes into one commit.

Privacy

Everything you type is processed in your browser. Nothing you enter is sent to our servers or stored by us. There's no account to create and nothing to install.

Frequently asked questions

Which type should I use?

feat for new features, fix for bug fixes, docs for documentation, refactor for code changes that don't change behaviour, and chore for maintenance.

When do I mark a breaking change?

When users of your code must change something to upgrade — that triggers a major version in semantic versioning.

Is a scope required?

No, it's optional. Use it to name the area changed, like (auth) or (api).

Content last updated . See how M2Toolkit works.

Other tools people use alongside the commit message generator.