What problem does it solve? Branch protection is often declared in a file but never actually enforced on the platform, leaving the default branch writable without review or passing checks. This Skill records the required GitHub ruleset in the repository and applies it through the GitHub API, closing the gap between stated policy and enforced protection. ## Core Features & Use Cases - Register-driven ruleset generation: Reads CI-001 requirements from controls.yaml and renders them into a stamped .github/rulesets/default-branch.json record, so the register is the single source of truth. - Confirmed platform mutation: Creates or replaces GitHub rulesets via the API only after an explicit per-call confirmation of blast radius, and migrates legacy classic branch protection safely. - Checker-based verification: Runs register-check run --control CI-001 afterwards and reports its verdict verbatim, distinguishing verified enforcement from credential-skipped checks. - Use Case: While adopting a control standard across a repository, you need the default branch to require pull requests and passing status checks. Run this Skill to record the ruleset, confirm the change, apply it to GitHub, and verify enforcement in one audited flow. ## Quick Start Ask the assistant to deploy gate-repo against the current repository so the default branch is protected by the ruleset the register requires.
