Body (optional, ≤72 chars/line recommended)
Templates
📝
git commit formatter,
Git Commit Bericht Formatteerder
Genereer Conventional Commits formaat commit berichten in een GUI.
Met emoji en tekenlimiet controle.
📝
Conventional Commits
GUI selection for feat/fix/chore and more
🎨
Gitmoji Support
Add emoji to commits for visual clarity
✅
Char Count Check
Real-time subject 50 / body 72 char limits
Commit Type
✨ Generated Message
⚠️ Subject=50 and body=72 characters are Git conventions (recommended, not mandatory).
Misschien ook interessant
about,
About
A GUI tool for generating Git commit messages in the Conventional Commits format. Select a type, enter a subject, optionally add scope/body/footer and Gitmoji emoji, then copy the formatted result. All processing is done locally in your browser.
how to,
How to Use
STEP 1
Choose a Commit Type
Select from 11 types: feat (feature), fix (bug), docs, style, refactor, etc.
STEP 2
Write Subject & Body
Describe the change briefly in the Subject. Add details in the Body if needed.
STEP 3
Copy & Use
Click Copy and paste the message into your git commit editor.
glossary,
Glossary
- Conventional Commits
- A specification for structured commit messages: <type>(<scope>): <description>. Enables automatic CHANGELOG generation and SemVer determination.
- Gitmoji
- A convention of prefixing commit messages with emoji to visually indicate the change type. ✨ = feat, 🐛 = fix, etc.
- Subject
- The first line of a commit message. Recommended to be ≤50 chars. Describes "what changed" in imperative form.
- Body
- Detailed explanation of the change, separated from Subject by a blank line. Each line should be ≤72 chars.
- Footer
- References issues/PRs (Closes #123) or declares BREAKING CHANGE.
- scope
- An optional keyword indicating the area of change. E.g., feat(auth) means a feature in the authentication module.
- BREAKING CHANGE
- A change that breaks backward compatibility. Marked with ! after the type or declared in the Footer.
- SemVer
- Semantic Versioning. Combined with Conventional Commits, tools like conventional-changelog can auto-determine version bumps.
faq,
FAQ
- Q.Is my input sent to a server?
- No. All message generation happens locally in your browser. Your code and commit content never leave your device.
- Q.Can I add custom commit types?
- The tool supports the 11 standard Conventional Commits types. For custom types, type them directly in the generated output.
- Q.How do I use it with Git hooks?
- Pair this tool with commitlint (commit-msg hook) to enforce Conventional Commits format across your team.
- Q.Is there a VS Code extension for this?
- Yes, the Commitizen VS Code extension. This tool's advantage is instant browser access without any installation.
- Q.Can I write commit messages in non-English languages?
- Yes. The tool fully supports input in any language. Please follow your team's conventions.
use cases,
Use Cases
🔍
Improving Code Review Quality
Consistent commit messages help reviewers instantly understand the intent of each change.
📊
Preparing for Automated CHANGELOG
Build a Conventional Commits history so tools like conventional-changelog can auto-generate versioned CHANGELOGs.
👨🏫
Enforcing Team Commit Standards
Onboard new team members to commit conventions with a hands-on, interactive reference.
🎓
Learning Git Best Practices
Understand commit message structure by building real messages with guided input.
Feedback sturen
Laat ons uw mening weten om ons te helpen de tool te verbeteren.
Feedback succesvol verzonden. Bedankt voor uw medewerking!
Er is een fout opgetreden. Probeer het later opnieuw.
Feedback wordt tijdelijk opgeschort
De server is overbelast of spambeveiliging is actief. Probeer het later opnieuw.