release-gate-chair
Runs the three pre-launch passes in order — web-preflight for external exposure, pre-ship-security-red-team for application behaviour in an isolated environment, pre-ship-performance-audit for measured speed — records each lane's own verdict and findings into one ledger, and computes a single release posture (HOLD or ready) with a script rather than judgement. Use when someone asks "is this safe to launch", "ready to ship", "should we deploy", "give me a go/no-go", or before any deploy of a site or client app you own or are authorized to test. Three verdicts stay separate; a pass in one lane never covers another. Variant: this fork runs the lanes itself and copies their finding tables verbatim; it is the default release gate. Not for a single-lane check (invoke that skill directly), for reports that already exist (use release-gate-validator), for penetration testing of production, or for performing the deploy.
Pinned to revision 8f64a143ab8a, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/release-gate-chair/SKILL.md
- skills/release-gate-chair/.gitignore
- skills/release-gate-chair/references/ledger.md
- skills/release-gate-chair/scripts/check_gate.mjs
Every link opens the file at its source, pinned to the revision this page describes.