Loading page
About this tool
A tool to help developers create conventional commits with standardized formatting
Conventional Commit Builder assembles a commit message in the Conventional Commits format — `type(scope): subject`, followed by a blank line and an optional body — from four separate fields so the punctuation and spacing are correct every time. It offers the ten standard types (feat, fix, docs, style, refactor, perf, test, build, ci and chore) and drops the parentheses automatically when you leave the scope empty. It is for developers on a repo where commitlint, semantic-release or a changelog generator expects that exact shape.
Open Conventional Commit Builder on AltFTool — it loads instantly in your browser.
Choose an entry in the 'Commit Type' dropdown. Its options are spelled out in full — New Feature, Bug Fix, Documentation, Code Style, Code Refactoring, Performance Improvement, Test Addition, Build System, Continuous Integration and Miscellaneous — and they write the prefixes feat, fix, docs, style, refactor, perf, test, build, ci and chore.
Fill in 'Commit Scope', 'Commit Subject' and 'Commit Body'. All three start empty and all three must be filled before anything is generated; until then the output panel reads "Enter Commit Scope, Commit Subject, Commit Body to see the result." Your scope is wrapped in parentheses straight after the type, and the body is appended after a blank line.
Read the assembled message under Result, with Type, Scope, Subject and Body broken out beneath it, then use Copy or Download. Click the 'Example' preset in the Examples row to load feat(login): add login button with a matching body if you want to see the shape of the output first.
The scope is wrapped in parentheses only when you supply one, and the body is preceded by a blank line — the two places hand-typed conventional commits usually break.
The type picker spells out what each prefix means, so you are choosing 'Performance Improvement' rather than guessing between perf, refactor and chore.
Type, scope, subject and body are edited independently and shown back to you as a breakdown, which makes a mistyped scope obvious before you commit.
`type(scope): description`, with an optional body after one blank line and optional footers after another. The type and description are required; the scope in parentheses is optional, and there is exactly one space after the colon.
This builder offers ten: feat, fix, docs, style, refactor, perf, test, build, ci and chore. The Conventional Commits 1.0.0 specification only mandates feat and fix — the rest are the widely adopted set from the Angular convention, and projects are free to add their own.
Under semantic versioning, a fix commit bumps the PATCH version, a feat commit bumps MINOR, and a breaking change bumps MAJOR. That mapping is what lets tools like semantic-release choose the next version from the commit log alone.
Add a `!` before the colon — `feat(api)!: drop v1 endpoints` — or add a `BREAKING CHANGE: <explanation>` footer at the end of the body. This builder does not add either for you, so type the `!` into the scope-and-subject text or append the footer in the body field.