About the Git Commit Message Generator
Vague commit messages like 'fixed stuff' or 'updates' make reviewing git history and generating automated changelogs nearly impossible. The Conventional Commits specification provides a lightweight convention on top of commit messages, creating an explicit commit history that integrates seamlessly with automated semantic versioning tools.
This Git Commit Message Generator helps you structure clean, semantic commit messages following the Conventional Commits 1.0.0 specification. It supports standard commit types ('feat', 'fix', 'docs', 'style', 'refactor', 'perf', 'test', 'build', 'ci', 'chore'), optional scopes, 50-character subject length tracking, detailed bodies, breaking change footers, and issue references.
To use it, select your commit type, enter an optional scope (e.g. 'auth'), type a concise imperative summary in the subject line, and add an optional detailed body or issue reference. The tool generates both the formatted commit message and a complete 'git commit -m "..."' command ready to run.
For example, selecting 'feat' with scope 'auth' and description 'add oauth2 login integration' produces: 'feat(auth): add oauth2 login integration'.
A common mistake in commit messages is using past tense ('added feature') instead of imperative present tense ('add feature'). The imperative mood matches the convention used by Git's own built-in commands ('Merge branch...').
Tip: Keep the subject line under 50 characters so it displays cleanly in GitHub pull request lists and terminal logs.