git-commit

Conventional commits automate message generation by analyzing your staged and unstaged changes to create standardized messages following the type(scope): subject format. This Skill generates these messages automatically when you indicate you're ready to commit, eliminating manual crafting while ensuring consistency across your repository.

Conventional Commits is a specification for commit message structure—type(scope): subject with optional body and footer—that makes commit history machine-readable and human-friendly. It enables automated changelog generation, semantic versioning, and clearer project history that tools can parse for automation and tracking.

Yes. This Skill integrates with Git environments supporting git status, git diff, and git branch commands, and aligns commit generation with project-specific standards and branching workflows. It analyzes your current branch and staged changes to suggest appropriate scopes and commit types that fit your established conventions.

The Skill analyzes code diffs to infer affected modules and generate context-aware scopes, then determines the commit type (feat, fix, etc.) based on the nature of changes detected. It surfaces appropriate scopes and handles breaking changes by including them in the commit footer when present.

The Skill handles both staged and unstaged changes, but you can use git add to stage specific changes first if you want finer control over what gets included in each commit. It accesses both states via git status and git diff to generate complete and accurate conventional commit messages.

Breaking changes are automatically detected and included in the commit footer as BREAKING CHANGE: notation, ensuring they're flagged clearly in your conventional commit message. This maintains specification compliance and signals semantic versioning implications to automation tools and users reviewing your history.