review

Review Mode

REVIEW MODE — Code review via Oracle activated.

Required actions:

1. Run git diff (or git diff HEAD~1) to capture the actual changes
2. Fire exactly ONE Oracle Agent call — include the full diff output in the prompt
3. Do NOT create multiple oracle calls (one per file, one per concern, etc.)
4. Oracle reviews the diff directly — it will read files only if needed for additional context
5. Collect Oracle's review before marking the task complete
6. Address any Critical or High severity findings before delivering

Review pattern:

// Step 1: Get the diff
Bash("git diff")  // or git diff HEAD~1 for committed changes

// Step 2: Fire ONE oracle agent with the diff included
Agent(
  subagent_type: "oracle",
  description: "Review recent changes",
  prompt: "Review this implementation. Here is the git diff:\n\n```diff\n[actual diff output]\n```\n\nFocus on correctness, security, regressions, and architecture fit."
)

// Step 3: Wait for verdict -> address Critical/High findings -> deliver

Anti-patterns (DO NOT do these):

• Creating separate oracle calls per file or per concern area
• Invoking oracle with just file names and no diff/code content
• Running multiple review passes or follow-up oracle calls

Verdict categories: Ship it / Ship with minor fixes / Needs changes / Needs rethinking.

Now execute the review. $ARGUMENTS

Get the git diff, fire one Oracle agent with the complete diff, and report the verdict.