>_ tools --commits

Conventional Commits Helper

Describe a change and get a proper Conventional Commit message - type, optional scope, subject, body, BREAKING CHANGE footer, and issue references - plus a ready-made PR title. Everything runs in your browser; nothing is uploaded.

DESCRIBE YOUR CHANGE

COMMIT MESSAGE

feat

PR / MERGE TITLE

no server · conventional commits 1.0.0 · feat → MINOR, fix → PATCH, BREAKING CHANGE → MAJOR · nothing is uploaded
JSON Formatter Inspect the config and payload files your commit touches. Debug Log Analyzer Find what actually failed before you write the fix() message. .htaccess → Nginx Converter For chore(ci) and build commits - convert the server rules. SQLite ⇄ MySQL Converter Schema migrations deserve their own refactor() commit.

>_ FAQ

What does each conventional commit type mean?

feat = a new feature (bumps MINOR); fix = a bug fix (bumps PATCH); docs/style/refactor/perf/test/chore/ci/build cover documentation, formatting, non-functional change, performance, tests, and tooling respectively. A BREAKING CHANGE footer or a `!` after the type bumps MAJOR.

How long should a conventional commit subject line be?

Keep the subject line to 50 characters or fewer - put detail in the body. The helper warns you if the subject grows past 50 characters.

Is my commit message sent anywhere?

No - the generator runs entirely in your browser. Nothing is uploaded, logged, or stored; close the tab and it is gone.