Parallel adversarial code review
review-fanoutworkflowsetup L3★1,223
sceneview/sceneview ↗What it does
Adversarially verify pre-merge SceneView PR review findings
Best for
Autonomous merge gates for SceneView PRs: reviewers catch issues, adversarial verify filters false positives, breaking-API change blocks auto-merge with traceback.
Inputs
- · [object Object]
Outputs
- · [object Object]
- · [object Object]
Requires
- · git diff (fetch origin --quiet first)
- · 4 dedicated reviewer agent types (code, security, impact, doc-freshness)
- · .claude/agents/<type>.md (fallback if agent type unavailable)
Preconditions
- · origin/main is fetched and available for diff
- · 4 reviewers run in parallel (code, security, impact, doc)
- · Each ERROR finding is immediately adversarially verified (pipeline barrier)
- · Verification can REFUTE errors (real=false) or confirm (real=true)
- · Reviewer unavailable → fallback to .md role file
Failure modes
- · FALSE POSITIVE error claimed (e.g., call-site guards it safely) → adversarial verify refutes it with real=false
- · Reviewer entirely fails → null result → REVIEW_INCOMPLETE fires (never false MERGE)
- · Breaking public-API change not detected → api-consistency lens reviews this
- · Rendering regression missed → impact-reviewer audits renderer touch
- · Threading violation not caught → code-reviewer checks Filament JNI explicitly
Trust signals
- · ERROR findings verified adversarially before MERGE recommendation (not just asserted)
- · Breaking-API change blocks auto-merge (human review required)
- · Reviewer unavailable → safety fallback to .md file (never silently dropped)
- · Per-reviewer mandate lives in .claude/agents/ (testable, versioned)
- · Pipeline barrier: verify each ERROR immediately (no batching false positives)