← ClaudeAtlas

reviewlisted

Verify a `review-ready` work item (or an entire batch) meets every acceptance criterion and every Quality Bar gate. Reject by default — each check requires cited evidence. Must run in a session distinct from the `/implement` session that produced the item.
opendatadiscovery/odd-team · ★ 0 · AI & Automation · score 75
Install: claude install-skill opendatadiscovery/odd-team
# Review Work Item / Batch You are reviewing `$ARGUMENTS`. The item (or batch) is in `status: review-ready`. Your job is to flip it to `done` **only** if every gate below passes with cited evidence. The default verdict is **rejection**. "Looks fine" is not a verdict. This skill exists because `/implement` is not allowed to self-close items. The lesson is `retrospectives/LSN-002-minio-region-unset.md` — every item closed before the separate-session-review rule was self-closed by the same session that implemented it. ## Hard prerequisites Refuse to run if any of these are true: - `$ARGUMENTS` is empty → list every `review-ready` item and ask which to review. - The work item status is not `review-ready` → print the status and stop. - **You are the same session that implemented the item.** If `/implement` and `/review` were called in the same session without an intervening boundary, stop and surface that — self-review defeats the gate. - The work item's commit is missing a `Sources:` footer (or the legacy `Consumer-read:` footer) **and** the item's claims are factual → reject immediately with "missing Sources footer" and set status to `blocked`. Pure prose-polish items with `Sources: none (prose polish, no factual claim)` are exempt. ## What to load 1. `CLAUDE.md` — universal framework + Quality Bar overview. 2. `pillars/{active}/{pillar,gates,authoring,canonical-homes,cornerstones}.md` — pillar rules. 3. `backlog/README.md` — status transitions. 4. The work item file — st