What problem does it solve? It prevents common Git mistakes—committing unintended staged files, misjudging merge status in squash-merge repos, and producing non-compliant commit messages—by enforcing conventional commit standards, branch naming rules, and safety checks at the moment of decision. ## Core Features & Use Cases - Conventional Commit Preparation: Analyzes staged changes, generates compliant commit messages with type, scope, and breaking-change footers, and verifies the staged set matches intent before committing. - PR Description Generation: Gathers branch context, runs a self-review checklist for secrets and debug artifacts, and produces a structured PR description with summary, impact, acceptance criteria, and testing sections. - Branch Strategy Validation: Enforces {type}/{descriptive-slug} branch naming mapped to semantic release version impact, and blocks work directly on protected branches. - Use Case: Before committing in a shared clone with parallel sessions, the skill verifies git diff --cached --name-only matches the intended file set, preventing another session's work from being swept into your commit. ## Quick Start Ask the assistant to prepare a conventional commit for the currently staged changes and confirm the staged file set before committing.
