What problem does it solve? Teams working on the SEIS repository risk claiming GitHub readiness without evidence, mixing local check results with GitHub check results, or bypassing branch and review governance. This Skill enforces a disciplined workflow so branches, pull requests, CODEOWNERS, and CI checks stay aligned with GitHub as the source of truth. ## Core Features & Use Cases - Branch and PR Governance: Keeps main as the only permanent branch and routes changes through short-lived branches, PR templates, and CODEOWNERS review. - Evidence-Based Readiness: Requires inspecting branch protection, PR state, check runs, and workflow runs before claiming anything is pushed, merged, or protected. - Governance Check Routing: Directs Master Prompt and governance changes through the issue template, PR template, CI workflow, and local check scripts such as check-seis-master-prompt and check-open-source-governance. - Use Case: When preparing a governance change to the SEIS repo, use this Skill to plan the branch, run the focused local checks, open a PR with the correct template, and leave an explicit no-push gate if GitHub evidence is unavailable. ## Quick Start Use the SEIS GitHub workflow skill to plan a branch and pull request for my governance change and tell me which local checks and GitHub evidence I need before claiming readiness.