Automated Conventional Commits from Git Diffs

Maintaining a clean, semantic git history is essential for automated versioning and team collaboration, but writing perfect commit messages every time is a chore. This skill automates the analysis of your staged changes and generates professionally formatted messages following the Conventional Commits specification.

What it does

• Analyzes git diffs to understand the scope and intent of your changes.
• Classifies work into standard types: feat, fix, refactor, docs, style, test, and chore.
• Enforces the 50/72 rule (50 characters for subjects, 72 for body wrapping).
• Detects and highlights breaking changes with the required "!" syntax and footer.
• Writes in the imperative mood, ensuring consistency across your entire project history.

Why use this skill

Unlike generic AI prompting, this skill uses a specific decision heuristic to distinguish between nuances (like refactor vs. style) and handles complex git requirements like footers and issue references. It ensures your repository is ready for automated changelog generation tools like semantic-release.

Supported Workflows

This skill works with any standard Git environment. It can read staged changes, unstaged changes, or focus on specific file paths to provide the most accurate context for your commit message.