Conventional Commit Generator

Conventional Commits is a lightweight specification for writing standardized commit messages. Every commit begins with a type, an optional scope in parentheses, and a short description, in the form type(scope): description. The predictable structure makes commit history easier to read and, more importantly, easier for automated tools to parse.

The generator supports eleven types: feat for a new feature, fix for a bug fix, chore for build or tooling changes, docs for documentation, refactor for code changes that neither fix a bug nor add a feature, test for tests, style for formatting-only changes, perf for performance improvements, ci for continuous-integration changes, build for build-system or dependency changes, and revert for reverting a previous commit.

After the header line you can add an optional body, an optional BREAKING CHANGE note, and an optional footer. The tool places a blank line before each of these blocks, so the final message reads: header, blank line, body, blank line, BREAKING CHANGE, blank line, footer. Only the header — the type and description — is required.

The page pre-fills a complete example, feat(auth): add login with Google OAuth with a body and the footer Closes #123, #456, and regenerates the message live as you type. Copy it with one click and paste it into your terminal. All processing is client-side.

Key Concepts

• Type — a keyword such as feat, fix, or docs that classifies the change.
• Scope — an optional noun describing the affected area, e.g. auth or api.
• Description — a short, imperative summary after the colon.
• Body — optional details, separated from the header by a blank line.
• BREAKING CHANGE — optional notice of an incompatible change.
• Footer — optional metadata such as issue references.

1. Choose a type — Select one of the eleven commit types from the Type dropdown.
2. Add an optional scope — Enter the part of the codebase affected, such as auth, api, or navbar.
3. Write the description — Add a short, imperative summary. The type and description are required for output.
4. Add optional body, breaking change, and footer — Expand the message with details, a BREAKING CHANGE note, or issue references.
5. Copy the message — Click Copy and paste the result into git commit. The Example button loads a ready-made message.

Conventional Commits are widely adopted because a consistent message format pays off across the whole development workflow. Here are some of the most common reasons to use them.

1. Team commit standards — give every commit a consistent, reviewable shape.
2. Automated versioning — tools like semantic-release map types to major, minor, and patch bumps.
3. Changelog generation — produce release notes directly from the commit history.
4. Searchable history — filter commits by type or scope when investigating changes.
5. Contributor onboarding — make it obvious how to describe a change correctly.
6. Issue traceability — link commits to tickets through footer references.