Git Commit Message Helper

Conventional commit messages follow the format <type>(<scope>): <subject> to standardize your git history. This Skill analyzes your staged changes, determines the commit type (feat, fix, docs, style, refactor, test, chore), and generates a formatted message you can copy directly into git commit.

Conventional commits are a standardized format for commit messages that improves git history readability and enables automated version control tooling. They ensure consistency across teams and projects by classifying changes into predefined types like features, fixes, and documentation updates.

Yes. By generating standardized commit messages that follow the Conventional Commits template, this Skill ensures all team members produce consistent git history regardless of their individual practices, improving collaboration and tooling interoperability.

The Skill examines your staged changes using Grep to analyze what code was modified, then classifies the change as a feature, fix, documentation update, style change, refactor, test addition, or maintenance task, automatically selecting the appropriate commit type.

No. The Skill generates a complete commit message in the Conventional Commits format that you can use immediately. You can copy the output and run git commit, or adjust the message if your change requires additional context in the body or footer.

This Skill requires Grep to analyze staged changes in your repository. You need to have git initialized with staged changes ready, and the Skill will output a formatted conventional commit message ready for use.