Conventional Commit Formatter

Format commit messages following the Conventional Commits spec (feat/fix/chore/docs/refactor/...) with optional scope and breaking-change marker.

Build your commit

Type

Scope (optional)

Short description (required) Long body (optional, separate paragraphs with blank line) Breaking change note (optional) Mark as breaking change (!)

Formatted commit message

Conventional Commits reference

feat — new feature
fix — bug fix
docs — documentation only
style — formatting, whitespace (no code change)
refactor — neither feat nor fix
perf — performance improvement
test — adding or fixing tests
build — build system or external deps
ci — CI config files
chore — misc maintenance
revert — revert a commit

About Conventional Commit Formatter

Conventional Commits is a lightweight convention for commit messages built around a type prefix such as feat, fix, or chore, with an optional scope in parentheses. Standardized prefixes make history searchable at a glance and enable tooling to generate changelogs and semantic version bumps automatically.

Adopt it from the first commit of any project that ships releases or publishes packages. Always start with a valid type prefix, keep the subject short and in the imperative mood, and reserve feat and fix for changes that should affect the version number.