What problem does it solve? Merging a pull request without a consistent, enforced review process lets regressions, security issues, and unmet requirements slip through. This Skill acts as the final pre-merge gate: it runs the project's full check suite, routes the diff to the right reviewers, verifies their verdicts, and returns an explicit SHIP or HOLD decision with named blockers. ## Core Features & Use Cases - Gate round accounting: Counts each review round per branch against a configurable cap (default 2), refusing to run on dirty trees, missing upstreams, or unpushed commits so rounds are never wasted. - Diff routing and reviewer fan-out: Classifies the committed diff into deterministic, fast-path, or model lanes via a decision router, then launches the required reviewers (code-reviewer, prose-reviewer, security-scanner) with lane-independent triggers that can only add reviewers. - Verdict validation and coverage check: Parses each reviewer's JSON verdict, rejects malformed or incomplete reports, journals decisions to a run trace, and compares launched versus answered reviewers before walking the Definition of Done. - Use Case: Before merging a feature branch, invoke the gate to revalidate the branch against the remote default branch, run the test suite, fan out reviewers in parallel, and receive a HOLD listing the exact failing check and file:line blocker — or a clean SHIP. ## Quick Start Ask the agent to run the pr-ship gate on the current branch before opening the pull request and report the SHIP or HOLD verdict with any blockers.
