What problem does it solve? Pushing code to a shared or public remote without checks risks leaking credentials, private paths, internal persona names, or broken trees, and divergent local history can expose private work. This Skill enforces a sequence of pre-push quality gates so only verified, clean commits reach the remote. ## Core Features & Use Cases - Immutable Verification Gate: Runs tests, type checks, builds, and audits, then asserts the working tree and commit SHA are unchanged so side-effect writes cannot invalidate a pass. - Privacy and Secrets Scanning: Scans the committed tree, added diff lines, and reachable Git history for API keys, private keys, local paths, internal identifiers, and artifact directories. - Independent Closeout Review: Dispatches a read-only reviewer agent against an exact SHA, requiring actionable HOLD verdicts with file:line evidence before any push. - Clean Publication from Divergent History: Squashes long private local history into a single public commit, handles shallow-clone publication via commit-tree, and verifies pushed SHAs against ls-remote and the GitHub API. - Use Case: Before publishing a feature branch to a new public repository, run the gates to catch a leftover private profile name in history, squash dozens of internal commits into one clean commit, and confirm CI passes on the exact pushed SHA. ## Quick Start Ask the agent to run the pre-push quality gates on the current branch and verify it is safe to push to the shared remote.