What is the Conventional Commits specification?

Conventional Commits is a lightweight convention on top of commit messages that provides a set of rules for creating an explicit commit history. It uses the format: type(scope): description. The specification aligns with Semantic Versioning — feat maps to MINOR, fix maps to PATCH, and BREAKING CHANGE maps to MAJOR.

When should I use a scope?

Scopes are optional but highly recommended for larger codebases. Use a scope to indicate which module, component, or area of the project your change affects. For example: feat(auth): add OAuth login or fix(api): handle null response gracefully.

What does the BREAKING CHANGE flag do?

Checking 'Breaking Change' adds a BREAKING CHANGE: footer to your commit message and appends an exclamation mark after the scope — e.g. feat(api)!: change response format. This signals to automated tooling that the change is not backward-compatible and warrants a MAJOR version bump.

How does the diff analyzer work?

Paste any git diff output into the diff analyzer panel. The tool scans the added and removed lines for patterns — new functions, modified tests, config file changes, documentation updates — and suggests the most appropriate commit type and scope.

Can I use emojis in real git commits?

Yes — emoji characters are valid in git commit messages and display correctly on GitHub, GitLab, and Bitbucket. Many projects adopt the Gitmoji convention. The emoji prefix is purely optional and can be toggled off if your team prefers plain text.

Developer Free No signup

Git Commit Message Generator

Generate conventional commit messages following the Conventional Commits spec with type, scope, emoji prefix, breaking change flags, and issue references.

Loading tool…

About this tool

Craft perfectly formatted commit messages following the Conventional Commits specification without memorizing the syntax. Choose the commit type from the full list — feat, fix, docs, style, refactor, test, chore, perf, ci, build — each color-coded and explained. Add an optional scope to clarify which part of the codebase is affected and get smart scope suggestions based on the selected type. The tool suggests common scopes for each type: api, ui, db for feat; auth, parser, config for fix; readme, changelog for docs; and so on. Toggle the emoji prefix option to prepend a matching emoji (✨ feat, 🐛 fix, 📚 docs, 💄 style, ♻️ refactor, ✅ test, 🔧 chore, ⚡ perf, 👷 ci, 🏗️ build). Mark the commit as a breaking change to auto-insert the BREAKING CHANGE footer. Add issue references that auto-format as 'Closes #123'. The live preview updates with every keystroke showing exactly how the final commit message will look. A built-in diff analyzer lets you paste a git diff and suggests an appropriate commit type and scope. The Conventional Commits spec summary is always visible as a quick reference.

How to use

1 Select the commit type that best describes your change (feat for new features, fix for bug fixes, etc.).
2 Optionally select or type a scope to indicate the affected area of the codebase.
3 Enter a concise description in the imperative mood (e.g. 'add login button', not 'added login button').
4 Toggle emoji prefix, breaking change, and issue reference options as needed.
5 The live preview at the top shows the final commit message — click Copy to copy it to the clipboard.
6 To generate from a diff, paste your git diff into the Analyze Diff tab and click Suggest.

Frequently Asked Questions

Related tools

Git Command Cheat Sheet

Interactive reference of 80+ essential Git commands, organized by category with search and favorites.

Regex Tester & Debugger

Test regular expressions with real-time match highlighting, capture groups, and replace mode.

Text Diff Checker

Compare two text blocks and highlight additions, deletions, and changes — line-by-line diff with word-level highlighting.