What problem does it solve? Inconsistent commit messages, vague change descriptions, and unsafe Git operations make repository history hard to audit and risky to maintain. This Skill standardizes how commits are written, branches are named, and code is pushed so every change is traceable and reviewable. ## Core Features & Use Cases - Conventional Commits enforcement: Requires typed subjects (feat, fix, refactor, etc.) in English, lowercase, imperative mood, under 72 characters, with a mandatory body listing every changed file. - Branch and push workflow rules: Defines branch naming (type/short-description), protected branches (main, mobile), merge-only pulls (no rebase), and no force-push policies. - Pre-commit checklist: Requires typecheck and lint to pass, no console.log or any types, and exclusion of handoff/session files from commits. - Use Case: Before committing a new audio player feature in a React Native app, the Skill produces a compliant message like "feat: add custom audio player" with a full body listing created and modified files, then guides staging only task-related files and pushing the feature branch. ## Quick Start Before committing, ask the assistant to write a compliant commit message and verify the pre-commit checklist for the current changes.
