š What is this tool?
Git Commit Builder generates well-formatted conventional commit messages following the Conventional Commits specification. Select type (feat, fix, docs), add scope and description to generate commits compatible with automated changelogs and semantic release.
š” Example
Input
Type: feat | Scope: auth | Description: add OAuth2 login
Output
feat(auth): add OAuth2 login
git commit -m "feat(auth): add OAuth2 login"
š ļø Common Use Cases
- Write consistent conventional commit messages
- Generate commits compatible with semantic-release
- Follow team commit message standards
- Learn the conventional commits format
- Create commits that trigger changelog generation
ā Frequently Asked Questions
What are conventional commits? ā¾
Conventional Commits is a specification for commit message format: type(scope): description. Common types: feat (new feature), fix (bug fix), docs, style, refactor, test, chore. It enables automated changelog generation.
What is a breaking change commit? ā¾
Add ! after the type to mark breaking changes: feat!: remove deprecated API. Or add "BREAKING CHANGE:" in the commit footer. Tools like semantic-release detect this and bump the major version.
What tools work with conventional commits? ā¾
semantic-release (automated versioning), standard-version, conventional-changelog, and commitizen all work with conventional commits. GitHub Actions can auto-generate changelogs on each release.
š
Your data stays private. All processing happens entirely in your browser. Nothing is ever sent to our servers. You can use this tool offline after the page loads.