← ClaudeAtlas

code-review-adversariallisted

Deep code review via a committee of specialized reviewers with PR-type-aware playbooks and convergence. Feature PRs �� evaluate better alternatives; bugfix PRs → verify fix correctness + regression; design-heavy PRs (proto/contract only) → AIP/compatibility audit. Dispatches 2-4 reviewers from distinct stances, converges via collaborative arbiter, outputs structured verdict. Use for high-stakes PRs (concurrency, security, contract changes) or when the user asks for "深度评审", "对抗复核", "adversarial review", or "契约评审".
yuefanxiao/code-review-adversarial · ★ 5 · Code & Development · score 67
Install: claude install-skill yuefanxiao/code-review-adversarial
# code-review-adversarial Deep code review engine that dispatches a committee of specialized reviewers, converges their findings, and outputs a structured verdict. PR-type-aware: feature PRs are evaluated for better alternatives; bugfix PRs are evaluated for fix correctness + regression introduction. **Design doc**: `DESIGN.md` (in this skill's directory) — full design rationale, research references, and decision records. **Reference files** (loaded on demand): - `references/type-playbooks.md` — per-PR-type review checklists - `references/reviewer-personas.md` — reviewer persona prompt templates - `references/convergence-protocol.md` — convergence and arbitration rules ## When to use - High-stakes PR: concurrency, security, API/contract changes - User explicitly asks for adversarial / multi-agent / deep review - Feature PR where solution quality matters (is there a better approach?) - Bugfix PR where correctness and regression risk matter ## When NOT to use - Routine PR quick pass (use a single reviewer) - Pure merge/rebase with no logic changes - User wants fast feedback, not deep analysis (this is expensive: 2-4 sub-agents) ## Arguments Parse `$ARGUMENTS` loosely: - **PR target (required)**: `PR #<N>`, `#<N>`, `<N>`, or full PR URL (GitHub/GitLab/Gitea). - `reviewers:<comma-list>` — manually specify personas (overrides type-based auto-selection). Accepted tokens: `design`, `correctness`, `security`, `root-cause`, `regression`, `behavior`, `test-coverage`, `perf`,