DiffCheck

Conventional Commit 生成器

描述

A new feature

0/72
填写上方字段以生成提交信息
类型说明
featA new feature
fixA bug fix
docsDocumentation only changes
styleFormatting, missing semi-colons, etc.
refactorCode change that is neither a fix nor a feature
perfPerformance improvement
testAdding or updating tests
buildBuild system or external dependencies
ciCI configuration and scripts
choreOther changes that don't modify src or tests
revertReverts a previous commit

What Is the Conventional Commit Builder?

The Conventional Commit Builder is a free online tool that generates well-formatted commit messages following the Conventional Commits specification. Select a commit type, enter an optional scope, describe the change, and the tool assembles the correctly structured message ready to paste into your terminal or Git client.

Conventional Commits is widely adopted in open-source and enterprise projects because it makes the project history human-readable and machine-parseable. Tools like semantic-release, commitlint, and release-it rely on the format to automate versioning and changelog generation.

How to Use the Conventional Commit Builder

  1. Select the commit type that best describes your change (e.g. feat for a new feature, fix for a bug fix).
  2. Optionally enter a scope — the area of the codebase affected, such as auth or api.
  3. Check Breaking Change if the change is not backwards-compatible.
  4. Write a concise description in the imperative mood (e.g. "add login page", not "added login page").
  5. Optionally add a longer body and a footer with issue references or breaking change details.
  6. Click Copy to copy the full commit message.

Features

  • All 11 standard commit types with descriptions
  • Optional scope field
  • Breaking change flag (adds ! and BREAKING CHANGE: footer)
  • Header character counter with 72-character warning
  • Multi-line body and footer support
  • Live commit message preview
  • One-click copy to clipboard
  • Quick reference table for all types

FAQ

What is Conventional Commits?

Conventional Commits is a specification for writing standardized commit messages. It defines a simple format: <type>[optional scope]: <description>, with optional body and footer sections. Common types include feat (new feature), fix (bug fix), docs, style, refactor, test, and chore.

How do I indicate a breaking change?

Add an exclamation mark after the type/scope, e.g. feat!: drop support for Node 6. You can also add a BREAKING CHANGE: footer with a description of what changed. Tools like semantic-release use these markers to trigger major version bumps.

What is the commit scope?

The scope is an optional noun describing the part of the codebase affected, placed in parentheses after the type. Examples: feat(auth): add OAuth2 login, fix(api): correct null handling in user endpoint.

How long should a commit description be?

The conventional commits spec does not mandate a character limit, but the widely followed Git convention is to keep the header line under 72 characters so it renders cleanly in terminals and GitHub. This builder warns you when you exceed that limit.