AI Git Commit Message Generator

Conventional Commits is a specification for writing standardized commit messages. Each message starts with a type (feat, fix, refactor, etc.), an optional scope in parentheses, and a concise description. For example: 'feat(auth): add OAuth 2.0 login support'. This format enables automatic changelog generation, semantic versioning, and easier code review.

Select Auto-detect and the AI chooses based on your description. Common types include: feat for new features, fix for bug fixes, refactor for code restructuring without behavior changes, docs for documentation updates, test for adding or updating tests, perf for performance improvements, chore for maintenance tasks, and ci for CI/CD changes.

The imperative mood (like 'add feature' not 'added feature') is a git convention because it completes the sentence 'This commit will...' — for example, 'This commit will add OAuth 2.0 login support.' This creates consistency across your commit history and matches the style git itself uses for merge commits and rebases.

Include a body when the subject line alone does not fully explain the change. Bodies are especially valuable for explaining why a change was made (not just what), documenting alternative approaches that were considered, noting breaking changes, and referencing related issues or tickets. Simple changes like typo fixes usually only need a subject line.

When your team follows Conventional Commits, tools like semantic-release and standard-version can automatically generate changelogs from your commit history. feat commits become entries in the Added section, fix commits become Fixed entries, and commits with BREAKING CHANGE in the footer trigger major version bumps. Consistent commit messages make release management effortless.