nledford/engineering-review-board / skills/adversarial-review
adversarial-review
VerifiedSkeptically verify completed changes, agent work, merge readiness, and hidden regressions. Use after implementation when claims need independent proof; do not use as the primary implementation or ordinary code-review workflow.
Adversarial Review Skill
Use this skill for an independent final challenge after implementation or a
primary review is complete. Always load
review-verification-protocol
before reporting findings. Load code-review only
when the CodeRabbit CLI is the review tool for this change; skip it when
CodeRabbit already reviews the pull request on the hosting service.
Do not use it to implement changes, debug an active unexplained failure, or replace the first focused review of a diff. One independent review per change is enough: a reviewer subagent's review satisfies it, so don't add a second layer unless that review's evidence is missing.
Workflow
- Compare the request, acceptance criteria, diff, tests, documentation, and prior agent claims.
- Inspect the strongest available evidence instead of accepting summaries at face value. Don't re-run checks the report shows passing; run a targeted check only when a finding needs proof.
- Challenge one plausible hidden failure mode, including invalid states, untested boundaries, scope creep, and regressions.
- Report only findings supported by reproducible evidence. Distinguish blockers from follow-ups and explicitly clear disproved concerns.
- Record skipped checks, assumptions, and residual risk before recommending a merge or handoff.
Output
Return a merge recommendation with verified evidence, blockers, follow-ups, skipped validation, and assumptions that still need proof.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |