cut-releaselisted

Cut an agentic-foundry release as a guarded playbook (/foundry:cut-release). Encodes the hand-run cut procedure as a loop whose EXIT GATE is the existing acceptance verdict — verifies the ordered preconditions (plugin.json version, CHANGELOG section; the marketplace.json catalogue bump is deferred to the re-pin commit R2), refuses to emit any publish plan until run_acceptance returns pass, and only afterward emits the gotcha-correct publish plan (re-pin marketplace source.sha to the release commit → annotated tag on the re-pin commit → machine-verify the tag → push, never force) WITHOUT pushing. Trigger when the operator is cutting/releasing a version — "cut a release", "release v0.6.1", "/foundry:cut-release", "ship the release".
lukasrepublic/agentic-foundry · ★ 1 · AI & Automation · score 67

Install: claude install-skill lukasrepublic/agentic-foundry

# /foundry:cut-release — the cut-release playbook The FIRST foundry **playbook** (a guarded, looping skill — task-triggered, loop held by an **EXIT GATE**, floors orthogonal; see `docs/TERMINOLOGY.md`). It turns the release-cut procedure — which lived only as memory-prose and was hand-run ~6× (every recurring gotcha was that procedure failing) — into a self-contained, gated loop driven by `scripts/foundry-cut-release.py`. Its EXIT GATE is the **EXISTING acceptance verdict** (`foundry-release-acceptance.run_acceptance`) — the only gate this script invokes; it reimplements no gate logic. The closure derivation (`foundry_release.py`) is **upstream prep the operator runs before the cut**, not invoked here. It adds **no new floor** and **never runs `git tag` / `git push`** — it emits the publish plan as data and the operator executes it. > **Retired: the wiring-pin migrate.** This loop once named a `foundry-wiring-hash.py` > wiring-pin migrate step, re-checked transitively via DOCTOR-GREEN. That mechanism — > `scripts/foundry-wiring-hash.py`, the `.foundry/wiring-hash.pin` file, and the doctor's wiring-hash > check — was retired; the current `foundry-doctor.py` (a thin 5-check > probe, `skills/doctor/SKILL.md`) carries no wiring-hash check to re-check. What carries the load > today is the `foundry-release-acceptance` gate (`run_acceptance`) this loop's EXIT GATE already > calls. See `skills/release/SKILL.md`'s "Gate-wiring pin & manifest" tombstone for the fuller history. ## T