Git Commit Message Generator
Generate Conventional Commit messages (feat, fix, docs, refactor) instantly.
Git Conventional Commit Generator
feat(auth): add OAuth2 login provider
About Git Commit Message Generator
The Conventional Commits Message Builder formats standardized Git commit messages following the Conventional Commits 1.0.0 specification (`feat(auth): implement JWT refresh token flow`) with breaking change footers and issue tracker links.
How to Use Git Commit Message Generator
Step 1
Select the commit type (e.g. feat for new features, fix for bug fixes).
Step 2
Enter optional scope (e.g. auth, db, ui) and a concise subject line in imperative tense.
Step 3
Optionally add a detailed body explanation or breaking change footer.
Step 4
Click "Copy Commit Message" or "Copy git commit -m Command".
Practical Use Cases for Git Commit Message Generator
Semantic Release & Automated Changelogs
Construct structured commit messages that enable semantic-release and standard-version to automatically bump SemVer versions and generate CHANGELOG.md.
Professional Git History & PR Clarity
Maintain clean, human-readable repository commit histories that clearly communicate scope and intent.
Input & Output Examples
Formatting Feature Commit with Scope
Type: feat, Scope: api, Subject: "add rate limiting headers", Issue: "#88"
feat(api): add rate limiting headers\n\nCloses #88
Key Features & Performance
- ✓Conventional Commit types: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, `revert`.
- ✓Optional Scope builder (`feat(scope): ...`) and Breaking Change toggle (`feat!: ...` / `BREAKING CHANGE:`).
- ✓Interactive body explanation and ticket footer (`Closes #123`).
- ✓Character counter alerts when subject line exceeds the recommended 50/72 character limit.
- ✓100% Client-Side generation.
- ✓1-Click Copy formatted commit message.
Key Terminology & Definitions
Conventional Commits 1.0.0
A specification for adding human and machine readable meaning to commit messages following a structured `type(scope): subject` format.
Imperative Mood in Commits
Writing subject lines as commands (e.g. "add feature" instead of "added feature" or "adds feature") to match Git's internal commit messaging style.