Menu
Adversarial code review — find bugs, style issues, SDK misuse, then challenge findings
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Pre-PR pipeline — version bump check, changelog, lint, build, and diff summary
Phase 3 review — find unnecessary code, abstractions, and dead paths, then simplify
Phase 1 planning — read docs, read source, write implementation plan
Phase 4 verification — lint check then full dual-backend build verification
Adversarial code review with two passes. First finds issues, then challenges each finding to eliminate false positives. Use before merging.
Review and simplify recent code changes. Remove unnecessary abstractions, dead code, and complexity while preserving behavior.
| name | code-review |
| description | Adversarial code review — find bugs, style issues, SDK misuse, then challenge findings |
| user-invocable | true |
| allowed-tools | ["Read","Glob","Grep","Bash"] |
Adversarial Code Review
Review the staged or recent changes with a critical eye.
Pass 1 - Find issues:
git diff to identify them).documentation/PROC_MI_MODULES_REFERENCE.md).Pass 2 - Challenge findings: 4. Re-examine each finding. Is it a real problem or a false alarm? 5. Drop false positives. Keep only actionable issues.
Report: list confirmed issues, each with file:line and a fix suggestion.