← Back to Home
δΈ­ζ–‡ English

πŸ“ Conventional Commits Generator

Generate Conventional Commits v1.0.0 compliant Git messages following Angular conventions

🏷️ Commit Type

βš™οΈ Commit Details

πŸ’₯ Breaking Change
Area of change, lowercase English, hyphenate multi-word scopes
Required. Use imperative mood, lowercase first letter
For issue references or breaking change declarations, separate with newlines

πŸ“‹ Generated Commit Message

feat: add new feature

πŸ•’ History (local storage)

No history yet

πŸ“– How to Use

1. Select commit type: feat, fix, docs, etc.

2. Optionally enable Breaking Change (triggers MAJOR version bump)

3. Fill in Scope (optional), Description (required), Body and Footer

4. Preview the generated commit message in real-time, copy with one click

5. Commit command: git commit -m "<paste message>"

❓ FAQ

Q: What are Conventional Commits?
A: A Git commit message spec in type(scope): description format, enabling structured, automatable commit history.

Q: How to mark a Breaking Change?
A: Two ways: 1) Add ! after type, e.g. feat!:; 2) Add BREAKING CHANGE: description in footer. Both can be used together.

Q: What should Scope be?
A: Optional. Indicates area of change like auth, parser. Lowercase English, hyphenate multi-word.

Q: Does it pass commitlint validation?
A: Yes! Fully compliant with Conventional Commits v1.0.0, passes commitlint and similar tools.

Q: What goes in the Footer?
A: Breaking Change declarations and issue references like Closes #123.

πŸ“˜ Reference: Conventional Commits v1.0.0  |  Angular Commit Convention