← ClaudeAtlas

superstack-reviewlisted

Use before trusting or shipping an answer, design, plan, analysis, or risky code change — when you are about to commit to it. Also when the user asks for a review, a red-team, a second opinion, or to check work adversarially. For pure code diffs, prefer a dedicated code-review command when the environment has one; this runner covers every other artifact and needs nothing installed.
debabsah/superstack · ★ 2 · Code & Development · score 73
Install: claude install-skill debabsah/superstack
# superstack-review Don't self-vibe-check. **Manufacture blind adversaries** — fresh context, none of your rationale — and let them attack the actual work. Uses only the built-in Agent/Task tool — no other plugin required. (For a pure code diff, a dedicated code-review command in your environment may be sharper for that narrow case; this runner needs nothing installed and covers every artifact — designs, plans, analyses, schemas, configs, prose.) ## Run it 1. **Run the deterministic checks first** — the acceptance oracle, tests, linters, validators. Don't spend a reviewer on what a tool catches; reviewers are for judgment. Between the two sit **different-kind checks** — types, property/invariant checks, a reference implementation, a dry run on real data — more independent of your blind spots than another model instance; prefer one where it exists. 2. **Size the panel to the risk tier** (the method skill's table): **T2 → one lens**, the dominant risk; **T3 → 2–5 lenses**. **The default first lens is the scope block's load-bearing unknowns** — attack what changes everything if wrong; generic lenses (correctness/logic, security, data/edge-cases, architecture, requirements-fit, ops) fill the rest. Going past the tier minimum needs a named reason — a specific unresolved risk, not thoroughness for its own sake. One concern per lens; no overlap. 3. **Dispatch one `superstack-lens` subagent per lens, all in a single message** (multiple Agent/Task calls in one turn = they run in pa