Conventional Commit Message Generator
Pick a type and scope, write the summary and bullets, and get a valid Conventional Commits message with the git command — the subject line is checked against the 72-character limit.
a new feature (minor version bump)
feat: …
Write a summary.
git commit \ -m "feat: "
Share what you shipped: post it on DEVAE with the commit and get a review in a live room.
How it works
The subject is assembled as type(scope)!: summary, following the Conventional Commits 1.0 specification.
The summary is validated: imperative mood hint, no trailing period, and a 72-character limit with a 50-character soft target.
Body bullets become wrapped paragraphs; a breaking change adds the ! marker and a BREAKING CHANGE: footer.
The git command uses one -m per paragraph so the message is preserved exactly. Nothing is uploaded.
Save snippets like this to your DEVAE profile and share them with collaborators. Free for individuals.
Sign up freeFrequently asked questions
A commit subject of the form type(scope): description, optionally with a body and footers. Types like feat and fix map to semantic-version bumps and changelog sections.
Keep it under 50 characters when you can and never over 72; GitHub truncates longer subjects in list views.
When the change requires users of your code to do something: a removed option, a renamed API, a changed default. Add ! after the type and a BREAKING CHANGE: footer explaining what to do.
Yes: “add”, “fix”, “remove”, not “added” or “fixes”. It reads as an instruction that completes “this commit will…”.
