← ClaudeAtlas

applylisted

Use when a staged proposal has been reviewed and signed off — REVIEW.md Step 3 ticked reviewed or provisional — and is ready to promote into the live contextualizer.
nick-railsback/skill-engine · ★ 2 · Code & Development · score 68
Install: claude install-skill nick-railsback/skill-engine
# Apply Promote a reviewed proposal into the live contextualizer. Atomic-rename per file. Preserve the `REVIEW.md` audit trail in the live tree. Refuse to run when the proposal has not been signed off, when the sign-off is `reject`, or when more than one Step 3 box is ticked. ## When to invoke After `/skill-engine:review <name>` has run, the user has filled Step 1 of `REVIEW.md`, re-run `review` to populate Step 2, ticked verdict boxes on each disagreement (optional — for the engine's own read; the engine does not consume these), and ticked exactly one Step 3 box (`reviewed` or `provisional`). ## Resolving `<name>` and `<install>` Same resolution as `/skill-engine:review`: `<name>` is the slug without the `-context` suffix; bare invocation works when exactly one `*-context.proposed/` exists under `<install>`. See `review/SKILL.md` § Resolving `<name>` for the full rule. ## Pre-promotion gates Run these in order; any failure halts the apply and exits non-zero without mutating either tree: the manifest exists and parses, `REVIEW.md` exists and parses, the review loop actually ran (not just a ticked box — two literal-content checks against Step 1/Step 2), exactly one Step 3 box is ticked and it isn't `reject`, and the live tree hasn't changed since staging (per-entry content-hash comparison against the manifest's `sha_before`/`sha_after`). The exact checks, halt messages, and per-status hash rules are in [`references/pre-promotion-gates.md`](references/pre-promotion-gates