← ClaudeAtlas

simplicio-reviewlisted

Deep, adversarial branch review — parallel subagents on separate rubrics (security/correctness, code-quality, and does-it-reproduce), spawned in one message, then deduped into one verdict. Runs for EVERY item, no TRIVIAL/SMALL shortcut — it is 3 of the 6 roles in simplicio-tasks' minimum-agent floor. Use before merging any work, when the user says "review this branch/PR hard", "thermo-nuclear review", "is this safe to merge", or when simplicio-tasks needs the Step 4c adversarial verify gate. Scopes strictly to the diff; refutes rather than rubber-stamps.
wesleysimplicio/simplicio-loop · ★ 11 · AI & Automation · score 74
Install: claude install-skill wesleysimplicio/simplicio-loop
# simplicio-review — thermo-nuclear adversarial review A single reviewer rubber-stamps; independent reviewers refute. This skill runs the `simplicio-tasks` Step 4c adversarial-verify gate as a standalone, reusable review: it fans out parallel subagents on DISTINCT rubrics, each prompted to REFUTE, then synthesizes a single deduped verdict. Credit: distilled from cursor `thermos` (parallel background subagents, separate security vs code-quality rubrics, dedup-on-synthesis) wired into the simplicio evidence spine. ## When to use - Before merging ANY item, TRIVIAL through CRITICAL (the Step 4c gate) — `simplicio-tasks`' 6-agent floor (Step 3) has no solo/self-review path left; this fan-out is 3 of those 6 roles, always. - "review this branch hard", "thermo-nuclear", "find what's wrong before I merge". ## Step 1 — Gather context ONCE (parent) Collect, in the parent, so subagents don't each re-derive it: ``` git diff <base>...HEAD # the change set (clamp via simplicio-orient: stat + hunks) git diff --name-only <base>...HEAD # full contents of each changed file (signatures-only for unchanged neighbors) # the item body + acceptance criteria (simplicio-tasks Step 2b-1) # the run-verification evidence (Step 4b) + any existing PR review threads / bot comments ``` Scope is **added/modified lines only**. Pre-existing issues outside the diff are out of scope unless the change makes them reachable. ## Step 2 — Fan out parallel reviewers (one message, background) Spaw