What problem does it solve? It prevents accidental or unauthorized git mutations—such as pushes to main, force-pushes on shared branches, or AI-attributed commits—by enforcing a strict approval protocol and consistent commit conventions. ## Core Features & Use Cases - Approval-gated mutations: Requires explicit user approval before commits, pushes, branch creation, merges, rebases, tags, and destructive operations like reset --hard. - Branch protection: Hard-blocks all writes to main/master and mandates a typed branching model (feat/, fix/, chore/, refactor/, docs/, test/, perf/, ci/). - Conventional Commits and PR format: Standardizes commit messages, PR titles, and PR bodies with What/Why/How verified/Risk sections, and bans AI-attribution trailers. - Use Case: When an assistant is asked to commit and push a bug fix, it first outputs an impact summary covering branch, files changed, remote impact, reversibility, and collaborators, then waits for the user to reply "approve" before executing. ## Quick Start Ask the assistant to commit the current changes on a new fix branch and push it, and it will present an impact summary and wait for your approval before running any git command.
