What problem does it solve?
Inconsistent or non-compliant commit messages break CI/CD pipelines, make git history difficult to parse, and violate team coding standards, leading to wasted time during code reviews and release audits.
Core Features & Use Cases
- Commit Message Validation: Checks existing commit messages against the full Conventional Commits specification, flagging issues like invalid types, incorrect casing, overly long descriptions, or missing breaking change markers.
- Compliant Message Generation: Creates valid Conventional Commits messages from git diffs, lists of changed files, or plain-English change descriptions, auto-inferring the correct commit type, scope, and breaking change status.
- Use Case: A developer working on a bug fix can use this skill to turn a raw diff of changed authentication files into a properly formatted fix(auth): correct token expiration validation commit message that passes team CI checks, or validate a drafted message before pushing to avoid pipeline failures.
Quick Start
Use the clean-code-commit skill to generate a compliant Conventional Commits message from the diff of your recent changes to the payment processing module.