Adversarial code review — find bugs, style issues, SDK misuse, then challenge findings
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.
Plan a code change before implementation. Reads docs and source, produces a concise spec for human approval. Use for any non-trivial task.