Git Commit Message Generator

The Git Commit Message Generator is a free browser-based tool that helps you compose well-structured commit messages following the Conventional Commits specification. Instead of memorizing the format and typing commit messages from scratch, this tool provides a visual form where you select the commit type, optionally add a scope, write a short description, and include a body or footer as needed. The generated message updates in real time so you can preview exactly what will be committed.

Conventional Commits is a lightweight convention on top of Git commit messages that provides a standardized format. It works hand in hand with Semantic Versioning by tying commit types to version bumps: feat triggers a minor version bump, fix triggers a patch bump, and a BREAKING CHANGE footer (or ! after the type) triggers a major bump. This makes it possible for tools like standard-version, semantic-release, and conventional-changelog to automate versioning and changelog generation based on your commit history.

The tool supports all eleven standard commit types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert. It includes validation that warns you when your description exceeds 50 characters, starts with an uppercase letter, or ends with a period — all common style issues that linters like commitlint would flag. The body field includes guidance to wrap lines at 72 characters, matching the standard Git recommendation.

If you are working with Git repositories, you may also find the Git Command Builder useful for constructing complex Git commands, or the .gitignore Generator for creating ignore files. For comparing changes before committing, check out the Diff Viewer.

All processing happens entirely in your browser. No data is sent to any server — your commit messages, project names, and scope information never leave your machine. This makes it safe to use with proprietary codebases and sensitive project details.

1. Select a commit type from the dropdown (e.g. feat, fix, docs). Each type includes a short description of when to use it.
2. Optionally enter a scope to indicate the area of the codebase affected (e.g. auth, api, ui).
3. Write a short description of the change in 50 characters or fewer. The character counter turns yellow at 40 and red at 50.
4. Optionally add a body to explain the motivation behind the change. Keep lines at 72 characters or fewer for best readability in git log.
5. Toggle Breaking change if this commit introduces an incompatible API change. Add a description of what breaks and how to migrate.
6. Optionally add a footer for references like Closes #123 or Refs #456.
7. Click Copy or press Ctrl+Shift+C to copy the generated commit message to your clipboard. Paste it into your terminal with git commit -m "...".