Commit Type
0/50
Commit Message
Fill in the form to generate your commit message…
Build conventional commit messages interactively
Compose well-formed conventional commits with type, optional scope, breaking-change marker, body, and footer. Follows the Conventional Commits specification used by semantic-release and commitlint.
Frequently Asked Questions
- What are conventional commits?
- A specification for commit messages: type(scope): description, e.g. feat(auth): add token refresh. Machines can parse them to automate changelogs and version bumps.
- Which commit types exist?
- The core types are feat and fix; common additions include docs, style, refactor, perf, test, build, ci, and chore. feat triggers a minor release, fix a patch.
- How do I mark a breaking change?
- Add ! after the type/scope (feat!: drop Node 16) or a BREAKING CHANGE: footer. Either signals a major version bump to tools like semantic-release.
- Why bother with a commit convention?
- Consistent messages make history searchable, enable automated changelogs and releases, and force authors to state intent — which reviewers and future maintainers benefit from.