What problem does it solve?
It prevents broken, non-atomic, or poorly described commits by enforcing Conventional Commits discipline and running the repo’s required lint/build/test and pre-commit verification steps before anything is staged and recorded.
Core Features & Use Cases
- Conventional Commit enforcement: Keeps commit messages consistent and machine-parseable, making change history easier to review and automate.
- Pre-commit verification workflow: Runs the required checks in the correct order (lint first, then build, then tests, then internal reference validity) to catch issues before they reach CI.
- Operational commit hygiene: Ensures atomic change scope, avoids unintended staged files, and confirms required GPG signing is active; includes PR description upkeep after pushing.
Quick Start
Use this skill before every git commit by running its pre-commit checklist in order, then commit using a Conventional Commits subject formatted as type(scope): subject.