← ClaudeAtlas

release-gatelisted

Evaluate an exact release candidate against its approved Project Test Baseline and Release Delta, then return GO, GO WITH CAVEATS, or NO-GO without promoting it. Use when someone asks whether a candidate is ready to release. Triggers: "/release-gate", "is this ready to release", "run the release gate", "go or no-go".
haru3613/harness-ship · ★ 1 · AI & Automation · score 67
Install: claude install-skill haru3613/harness-ship
# release-gate Return a release verdict from existing evidence. This skill is read-only: it never merges, deploys, promotes, tags, publishes, seeds data, or changes release criteria. ## Required inputs Given the candidate's full source SHA, read these before asking the user for anything. Read the contract before asking for the SHA: a repository that does not own its release surface has no candidate SHA to give, and asking produces this repository's `HEAD`, which is the substitution the stop below exists to refuse. - `.harness-ship/test-contract.md` — the user-approved contract containing Project Test Baseline plus Release Delta. Gate against this file only. A `.harness-ship/test-contract.draft.md` beside it is an unapproved revision in progress and is never evidence, but its presence is also never a reason to reject a candidate the approved file covers. When this file is a pointer, follow it and gate against every document it names plus its `Carried here` field — that field is contract text approved with the pointer, carrying criteria the named documents never held, except its declarations about where the release surface is, what identifies a candidate, and what this repository can see of that owner: those pass or fail nothing, and the stop below acts on them instead. Its `Not carried by that document` field states what nobody has decided, and its entries are read by their label, not by whether they name a file: `undecided` and `unreadable` are unevaluat