requesting-code-review-codex

Requesting Code Review

Call the codex_review MCP tool to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.

Pass a structured prompt with the scope and reviewStyle fields matching the review type needed.

Core principle: Review early, review often.

When to Request Review

Mandatory:

• After each task in subagent-driven development
• After completing major feature
• Before merge to main

Optional but valuable:

• When stuck (fresh perspective)
• Before refactoring (baseline check)
• After fixing complex bug

How to Request

1. Get git SHAs:

BASE_SHA=$(git rev-parse HEAD~1)  # or origin/main
HEAD_SHA=$(git rev-parse HEAD)

2. Call codex_review:

Use one of these call shapes:

Structured review (base diff — requires base or commit scope; not available for uncommitted):

{
  "tool": "codex_review",
  "arguments": {
    "taskId": "task-17-review",
    "reviewStyle": "structured",
    "scope": { "kind": "base", "base": "origin/main" },
    "prompt": "Review Task 4 from docs/superpowers/plans/2026-04-03-agent-forwarding.md for correctness, regressions, and missing tests.",
    "workspaceRoot": "/absolute/path/to/your/repo"
  }
}

Advisory review (base diff):

{
  "tool": "codex_review",
  "arguments": {
    "taskId": "task-17-advisory",
    "reviewStyle": "advisory",
    "scope": { "kind": "base", "base": "origin/main" },
    "prompt": "Give concise advisory feedback on the diff since origin/main.",
    "workspaceRoot": "/absolute/path/to/your/repo"
  }
}