What problem does it solve? AI agents and developers working in Git repositories with protected main branches risk accidentally merging unreviewed code to production or pushing directly to main. This Skill prevents those costly mistakes by enforcing a strict working-branch-only policy and requiring explicit human approval before any merge or deploy. ## Core Features & Use Cases - Branch Protection Enforcement: All commits happen on a designated working branch (develop/dev), never directly on main. - Conventional Commit Messages: Standardizes commit format as type(scope): description with types like feat, fix, ui, refactor, docs, and chore. - Approval-Gated Merges: Merges to main and production deploys only occur when the user explicitly requests them. - Use Case: An AI agent is asked to "push the changes" after fixing a bug. Instead of merging to main, it commits fix(auth): handle expired session redirect to the dev branch and waits for an explicit merge instruction. ## Quick Start Ask the agent to commit your current changes to the working branch with a conventional commit message, without merging to main.
