pre-mergelisted

The CI gate. Takes a feature branch from "eng says done" to "PR open against staging with green checks". Runs the project's preflight-resolved pipeline from devkit/policy.json components[]: sync → parallel correctness + security waves → coverage → regression tail → security/migration → PRD-consistency → open PR. Emits a severity-graded verdict JSON. Absorbs the old /review and /test. Activates on /pre-merge after eng --build.
ndisisnd/msg · ★ 6 · Code & Development · score 79

Install: claude install-skill ndisisnd/msg

# pre-merge **The** CI gate. Runs after `eng --build` says a feature branch is done and takes it to a PR open against `staging` with green checks. Pre-merge holds **no human gate** — the human look at the running feature belongs to merge (`../shared/refs/safety-floor.md` § *Human gates*). Absorbs the retired `/review` and `/test`. Each run is independent. Posture: release engineer — owns the gate; repeatable evidence over assertion, severity matched to reachability, tables over prose, JSON-first. ``` eng --build → /pre-merge → (fail → eng --build report=…, repeat) → PR feature→staging → merge --staging ``` ## Usage - `/pre-merge` — gate the current feature branch against `staging` - `/pre-merge --init` — the one-time setup: detect tooling → interview → gated install/scaffold → write `devkit/policy.json`; no gate run (`refs/protocol-init.md`). The `.github/workflows/` CI pipeline is part of the detect unless `policies.github_actions.enabled` is `false` — a settled opt-out, not a gap - `/pre-merge --update` — reconcile the manifest with codebase reality: re-run preflight → diff `components[]` → approve the delta → apply `present`/`active_when`/new-component changes only, never re-grading user-set criticality or re-prompting settled opt-outs (`refs/protocol-init.md`) - `/pre-merge --update-criticality` — the criticality reconcile: inventory untagged tests → evidence-cited proposals → one human gate → markers committed + `criticality_review` restamped (`refs/protocol-