smart-commit

Conventional commit messages are standardized formats that include a type (feat, fix, docs, etc.), optional scope, and subject. This Skill generates them automatically from staged changes by analyzing your modifications, inferring the commit type and affected component, then formatting the message with proper structure, imperative mood, and character limits.

Conventional commits is a specification that structures commit messages with type, scope, and description to enable automated changelog generation, semantic versioning, and clearer project history. Using this format ensures consistency across your team and makes your Git history machine-readable and traceable.

Semantic commit messages map your changes to specific types (feat for features, fix for bugs, refactor for code restructuring, etc.) and extract the affected scope or module. This Skill enforces these rules automatically, mapping staged changes to the correct type, limiting subject lines to 50 characters, wrapping bodies at 72 characters, and appending footers for issue references.

Yes. This Skill generates conventional commit messages that include footer sections for issue references and breaking changes, allowing you to link commits to issue trackers. When you stage changes, the Skill automatically formats messages with closing keywords and issue numbers in the footer.

Stage your changes in Git using `git add` to prepare the modifications you want to commit. The Skill then analyzes those staged changes and generates a conventional commit message with the appropriate type, scope, subject, body, and footer based on the differences.

Conventional commits are Git-agnostic and work with any workflow—feature branches, trunk-based development, or trunk-based development. The Skill generates messages that conform to the standard regardless of your branching strategy; adoption depends on your team enforcing the format during code review.