What problem does it solve?
Inconsistent commit messages, failed quality checks, and untested code can lead to messy Git history, broken builds, and wasted development time. This Skill enforces a rigorous commit protocol, ensuring every change is thoroughly tested and adheres to project standards before being committed.
Core Features & Use Cases
- Automated Quality Gates: Automatically runs
lint and type-check before any commit, preventing common errors from entering the codebase.
- Guided Testing & Approval: Provides clear, actionable testing instructions and requires explicit user confirmation, guaranteeing code functionality.
- Conventional Commit Enforcement: Ensures all commits follow the project's conventional commit format, leading to a clean, readable, and searchable Git history.
- Use Case: After implementing a new feature, use this Skill to guide you through the final checks, ensuring your code passes all quality gates, is manually tested, and committed with a perfectly formatted message.
Quick Start
Use the commit-protocol skill to commit my recent changes to the 'mobile' app, after I have manually tested them.