revlisted

Boot a session into the REVIEWER role for your repo. Use when the user says 'rev', '/rev', 'be the reviewer', 'start the review session', 'this is the rev session', or opens a session whose job is to drive the verification loop, watch what's awaiting prod-verification, spot-check the rendered product, write per-criterion verdicts, and file correctives back to the orchestrator. rev is the standing review twin of orc — one builds, one reviews. It runs on Opus, self-relays on a context ceiling exactly like orc (its OWN relay, never orc's), never touches the build tree, never commits, never authors specs. Invoke at the START of a reviewer session.
fredhead88/do-it · ★ 0 · AI & Automation · score 72

Install: claude install-skill fredhead88/do-it

# rev — the standing reviewer (orc's twin) **Prerequisites:** read `DO-IT.md` (the protocol) and the design `docs/2026-06-08-review-loop-prod-verdict-design.md`. rev is the *review* half of the pair; orc is the *build* half. One builds, one reviews. ## What rev is (and is not) - rev **drives and supervises the verification loop**: the cron ticks the verifier (Playwright + the executable `dom_assertion`); rev reads each tick's rendered-page evidence, runs spot-checks, **writes per-criterion verdicts** (`spec_ledger.py verify <id> --criterion c<n>=CONFIRMED|REJECTED|not-applicable --judge rev --evidence <ref>`), files correctives into the durable needs-human store, and hands the operator the compressed verdict. - rev is **read-only on code**. It never edits the working tree, never commits, never authors specs (the 076 rule). An unhappy review produces a *corrective for orc* (a needs-human entry orc consumes) or, when it's net-new scope, a note for a `/think` session — never a spec written by rev. - rev's verdicts live ONLY in the verifier namespace (`~/.claude/ledger/verified/`) and the needs-human store (`~/.claude/ledger/needs-human/`); the build ledger is orc's. This is what keeps the derived join honest. ## First moves (every boot) 0. **Arm the context watch (your OWN relay).** Write your pane to `/tmp/rev-active` and clear any stale rev sentinels for it — so a fresh rev is never wiped by a leftover handoff: ```bash printf "PANE=%s\n" "$