Conventional Commit

Interactive generator for Conventional Commits with type, scope, breaking changes, and description.

0/72

Fill in the description to preview the commit message

Conventional Commits format

<type>[scope]: <description>

[optional body]

[optional footer(s)]

Common examples

About Conventional Commit โ€” Detailed Guide

The Conventional Commit Generator builds structured Git commit messages adhering to the Conventional Commits specification. It guides developers through selecting the Type, Scope, Subject line, optional Body description, and Footer issues.

Easily flag breaking changes with the exclamation syntax (`type!: description`), reference closed issues (`Closes #123`), and output standardized commit messages that empower automated tooling like `semantic-release` and automated changelog generators.

#git #commit #conventional #message #changelog

Key Features & Capabilities

  • Complete type catalog: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
  • Optional scope input and real-time subject length / imperative phrasing reminders
  • One-click Breaking Change toggle applying standard exclamation mark (`!`) syntax
  • Automatic issue linking footer generator with one-click `git commit -m` copying

How to Use

  1. 1

    Select the commit type (e.g. `feat` for features, `fix` for bug repairs).

  2. 2

    Provide an optional scope (e.g. `api`, `auth`) and a concise imperative description.

  3. 3

    Review the assembled commit string and copy the full `git commit` command for your terminal.

Common Use Cases

  • โ†’ Onboarding engineering teams onto consistent Git commit history standards
  • โ†’ Automating semantic version bumps and automated release notes with CI/CD pipelines
  • โ†’ Flagging backward-incompatible API breaking changes during major library updates

Related Tools

Frequently Asked Questions & Privacy

What semantic version bump corresponds to each commit type?

Under standard Conventional Commits conventions, `fix` triggers a PATCH bump, `feat` triggers a MINOR bump, and any commit with a `BREAKING CHANGE` triggers a MAJOR bump.

Should the subject line end with a period?

No. Conventional Commits best practices recommend a concise imperative sentence without a trailing period (e.g., `feat: allow user avatar upload`).