Release gate
Run the six ship gates (static, security, docs, tests, build, runtime smoke) across three agents, aggregated fail-closed into a SHIP/NO-SHIP verdict. /forge:ship fires this automatically; use it directly for a standalone pre-release check.From its SKILL.md
npx -y skills add travelhawk/forgeshift --skill release-gateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
/forge:release-gate — six ship gates, fail-closed verdict
Fire the release-gate workflow: static / security / docs checks in parallel, then
tests → build → runtime smoke sequentially, each returning evidence, aggregated fail
closed — a gate that doesn't report blocks the ship. Usually fired by /forge:ship; run
it directly for a standalone pre-release check.
- Resolve the plugin home once:
FORGE_HOME="${CLAUDE_PLUGIN_ROOT:-$(forge-home)}". Pass the target repo asdir(absolute) — the gates run real commands there, and workflows do NOT follow the shellcd. - Parse
$ARGUMENTSinto the release context (version + change summary), or an object{dir, context}. - Invoke: Workflow tool,
scriptPath: "$FORGE_HOME/.claude/workflows/release-gate.js",args: {dir: "<abs product root>", context: "<version + change summary>"}. - Relay the SHIP/NO-SHIP verdict with each gate's evidence. NO-SHIP blocks the release —
fix the blockers and re-run; never override. A
skippedTESTS gate means wrong directory or a broken setup, never an acceptable pass.
Next → /forge:ship on SHIP; fix the named blockers and re-run on NO-SHIP.