What problem does it solve? It prevents untracked, unsafe repository changes by enforcing a disciplined GitHub workflow where every task is recorded in an issue, implemented on an isolated branch, validated, and delivered as a pull request — with merging treated as a separate, explicitly authorized operation. ## Core Features & Use Cases - Issue-to-PR workflow: Resolves or creates a tracking issue, creates an isolated branch from origin/main, implements only the scoped work, validates changes, and opens a review-ready PR. - Gated merge operation: Merging is a distinct operation requiring its own explicit request and a specifically granted merge permission, never implied by a request to deliver a PR. - Safety contract: Prohibits direct commits to main, plain force-pushes, history rewrites on shared branches, and bypassing required checks or reviews. - Use Case: A user asks to implement issue #42 and open a PR; the skill reuses the existing issue, branches as issue/42-short-slug, runs the relevant tests, opens the PR, and reports merge readiness without merging. ## Quick Start Implement GitHub issue #42 on an isolated branch, run the relevant tests, and open a pull request without merging it.