What problem does it solve?
Developers often produce inconsistent, oversized, or unclear commits that slow code review and blur change intent; this Skill enforces conventional commit style and helps keep commits atomic and informative.
Core Features & Use Cases
- Branch safety: Detects when you're on master or main and offers to create a feature branch using the type/username/description pattern.
- Pre-commit validation: Runs project linters and build checks by default and respects a --no-verify flag to skip them.
- Smart commit composition: Inspects git status and diffs, suggests splitting unrelated changes into multiple commits, and generates emoji-enhanced conventional commit messages for each logical change.
- Use Case: Ideal for feature development, bug fixes, and chore updates where clear commit history, linting, and branch hygiene are required.
Quick Start
Create a conventional commit with emoji for the current changes and run the project's linters before committing unless I specify --no-verify.