What does Git Commit Generator do?
Build Conventional Commit messages with type, scope, body, breaking changes, and footers — copy-ready for git commit.
Free Git commit message generator for Conventional Commits — pick feat, fix, or chore, add scope and breaking changes, copy the message or a ready-to-run git commit command. Autosaved in your browser.
A conventional commit generator helps you write Git commit messages in the Conventional Commits format—type(scope): description—with optional body, footer, and breaking-change markers that changelog tools can parse.
Conventional Commits is a lightweight convention: `feat(auth): add login` tells humans and automation that a feature landed in auth. Tools like semantic-release read commit types to bump semver—feat → minor, fix → patch, BREAKING CHANGE → major.
EverydayTools Git Commit Generator walks you through type, optional scope, imperative subject line, body, footer (e.g. Closes #123), and breaking-change flags. Copy the result into `git commit -m` or your IDE. Nothing is uploaded; messages are built locally in your browser.
Build Conventional Commit messages with breaking-change support—isolated from semver bump calculators.
Concise answers for common searches — definitions, steps, and comparisons.
Build Conventional Commit messages with type, scope, body, breaking changes, and footers — copy-ready for git commit.
Yes. Messages are generated locally in your browser without uploading content to EverydayTools.
Select feat for features, fix for bugs, docs for documentation, chore for maintenance, or another Conventional Commits type.
Optionally narrow with a scope (auth, api, ui). Write a short imperative description — aim for 50 characters or fewer on the subject line.
Add a longer body for context, a footer like Closes #123, and enable breaking change when the API or behavior is incompatible.
Copy the formatted Conventional Commit or the full git commit command with -m flags for terminal paste.
Input
type: feat, scope: auth, description: add OAuth login, footer: Closes #412Output
feat(auth): add OAuth login
Closes #412A typical feature commit linking a pull request to an issue tracker entry.
Common real-world scenarios where this tool saves time.
Pick feat or fix, add scope, copy a valid message before git commit in terminal or VS Code.
Enable breaking change to produce ! and BREAKING CHANGE footer for semantic-release major bumps.
Add Closes #123 or Fixes #456 in the footer to auto-close tickets when merged on GitHub/GitLab.
Step-by-step chains that connect related tools for common tasks.
How this page compares for day-to-day Git workflows.
| Aspect | EverydayTools | Typical alternative |
|---|---|---|
| Format | Conventional Commits template | Blank git commit editor |
| Privacy | Browser-local | IDE-only, no guidance |
| Breaking changes | Built-in ! and footer | Manual formatting |
Use this tool to draft commit messages. For semver bumps after merging, use Semver Calculator.
| Related tool | Use this tool when | Use related tool when |
|---|---|---|
| Semver Calculator | You need a properly formatted Conventional Commit message before running git commit. | Commits are merged and you need to compare, bump, or sort semantic version numbers. |
| Markdown Editor | You are writing a Git commit subject and body. | You are authoring README or changelog Markdown with live HTML preview. |
Use imperative mood: "add login" not "added login" — it matches Git and Conventional Commits guidance.
Use refactor when behavior is unchanged; reserve feat for user-visible capability.
Expand the BREAKING CHANGE footer to explain what broke and how to migrate before pushing.
Fix: Your repo may enforce custom scopes or max length. Adjust scope and subject to match commitlint.config.js.
Fix: Move detail to the body. Keep the first line under 50–72 characters for readable git log and GitHub UI.
Advertisement
Conventional Commits use type(scope): description with optional body and footer. Types like feat and fix carry semver meaning; BREAKING CHANGE (or a ! after the type) signals a major bump for tools like semantic-release.
feat adds user-visible capability and typically bumps the minor version. chore covers maintenance—dependency updates, CI tweaks, repo housekeeping—that does not change production behavior or API surface.
When consumers must change code or configuration to upgrade—removed API fields, renamed env vars, changed default behavior. The generator adds ! to the subject and a BREAKING CHANGE footer you can expand before committing.
Aim for 50 characters or fewer on the first line; many teams accept up to 72. Use the body for detail. The workspace shows a live character count as you type.
Yes. Commit text is composed in your browser. EverydayTools does not upload your messages for normal use.
Commit text stays on your device during generation. Nothing is uploaded to EverydayTools servers.
Message formatting only — does not run git, enforce hooks, or validate your diff.
Advertisement
Reviewed by EverydayTools Editorial Team on 2026-06-02.