What problem does it solve? Coding agents often guess wrong about when to push: they either push shared or protected branches without permission, or leave finished work uncommitted and unpushed on solo repos. This Skill resolves a repository's publication policy into a concrete mode so every push decision follows the repo's actual rules instead of a generic ceremony. ## Core Features & Use Cases - Policy resolver script: Runs git-repo-policy against any repo to print facts (collaboration, visibility, default branch policy, push access) plus a derived mode and hygiene level, using git history and the GitHub CLI. - Five push modes: Classifies repos as local-only, auto-trunk, gated-trunk, pr-flow, or external, each with explicit rules about when pushing, branching, or opening a PR is appropriate. - Config overrides: Per-repo codingAgent.git.* git config values override auto-detection, with safe defaults (unknown visibility becomes public, unknown branch policy becomes pr-flow) when gh is unavailable. - Use Case: Before pushing work on an unfamiliar repository, run the resolver to learn it is a public shared repo with a protected default branch, then follow the pr-flow mode: branch, push the branch, and open a PR instead of pushing main directly. ## Quick Start Ask the agent to resolve this repository's push policy and tell you whether it is safe to push the current branch.