Conventional Commit Generator
Build formatted conventional commit messages (feat, fix, docs, refactor).
Git Conventional Commit & URL Converter
About Conventional Commit Generator
The Conventional Commits Message Builder creates standardized, semantic Git commit messages (`feat(auth): implement OAuth2 login (#123)`) compliant with Conventional Commits 1.0.0 for automated changelogs and semantic releases.
How to Use Conventional Commit Generator
Step 1
Select commit type (e.g. `feat`, `fix`, `chore`).
Step 2
Enter optional scope and concise imperative description (e.g. "add dark mode toggle").
Step 3
Optionally add body explanation and footer issue links.
Step 4
Click "Copy Commit Message" or copy terminal command.
Practical Use Cases for Conventional Commit Generator
Standardizing Git Commit Messages for Automated Semantic Releases
Construct compliant conventional commit messages that trigger automated version bumps (`fix` $\rightarrow$ patch, `feat` $\rightarrow$ minor, `BREAKING CHANGE` $\rightarrow$ major).
Generating Clean Git History & Release Changelogs
Format scope tags, short descriptions, body paragraphs, and issue closure references (`Closes #42`) for auto-generated release notes.
Input & Output Examples
Constructing Feature Commit with Scope and Breaking Change
Type: `feat`, Scope: `api`, Description: "add GraphQL endpoint", Breaking: true
`feat(api)!: add GraphQL endpoint\n\nBREAKING CHANGE: REST v1 endpoints deprecated.`
Key Features & Performance
- ✓Types: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, `revert`.
- ✓Interactive controls for Scope, Description, Detailed Body, Breaking Changes (`!`), and Issue Closes (`Fixes #12`).
- ✓Real-time character counter enforcing recommended 50/72 Git message length rules.
- ✓100% Client-Side memory execution.
- ✓1-Click Copy commit message or `git commit -m "..."` command.
Key Terminology & Definitions
Conventional Commits 1.0.0
A specification for adding human and machine readable meaning to commit messages, providing an easy set of rules for creating an explicit commit history.
Breaking Change Flag (`!`)
An exclamation point placed after the type/scope to immediately signal a breaking API change in automated semantic versioning tools.