What problem does it solve? Writing meaningful, convention-compliant commit messages is repetitive and often results in vague entries like "chore: update". This Skill analyzes your actual changes and drafts a properly formatted Conventional Commits message, so your git history stays consistent and informative. ## Core Features & Use Cases - Diff-Based Message Generation: Reads the staged diff (or unstaged if staged is empty) plus recent commit history to determine the correct type, scope, and subject language. - Convention Enforcement: Applies the full Conventional Commits ruleset — type selection (feat, fix, refactor, docs, etc.), kebab-case scopes, imperative subjects of 50-72 characters, and mandatory AI-attribution trailers. - Mixed-Change Detection: Detects when a diff combines unrelated changes (e.g., a fix plus a refactor) and suggests splitting them into separate commits instead of writing a misleading message. - Use Case: You finished fixing a login bug across two files. Instead of composing the message yourself, you ask for a commit — the Skill inspects the diff, proposes "fix(auth): correct token validation on login", and commits only after your confirmation. ## Quick Start Ask the assistant to commit the current changes following the Conventional Commits convention.
