Code Review

Focus on substantive issues: bugs, missing tests, complexity, performance, duplication, incomplete implementations. Skip linting concerns (formatting, imports, naming style).

External Review (Optional)

Check for external reviewers and use if available. Priority: Codex > Gemini

bash
1command -v codex >/dev/null 2>&1 && echo "Codex available"
2command -v gemini >/dev/null 2>&1 && echo "Gemini available"

If Codex available:

• Local branch: codex --config model_reasoning_effort="high" review --base BASE_BRANCH
• Remote PR: gh pr diff NUMBER | codex review --config model_reasoning_effort="high" -

If only Gemini: Pipe diff to gemini with review prompt.

Workflow

1. Get the diff

   • PR: gh pr view NUMBER --json title,body,files then gh pr diff NUMBER
   • Branch: git diff origin/master...HEAD
   • Uncommitted: git diff

2. Gather context - Read PR description, commit messages, project CLAUDE.md

3. Review each file for:

   • Completeness: All code paths handled? Stubs left behind?
   • Tests: Added? Meaningful? Edge cases covered?
   • Complexity: Justified abstractions? Simpler alternatives?
   • Performance: Hot path regressions? Unbatched I/O?
   • Duplication: Similar code already exists? (rg "pattern")

4. Synthesize external review (if used) with your findings. Consensus issues = high confidence.

Output Format

markdown
1## Summary
2[1-2 sentences]
3
4## External Reviewer
5[If used: Codex or Gemini]
6
7## Key Findings
8
9### Must Address
101. **[Issue]** (`file:line`) [Models]
11   - Details
12   - **Risk**: Why it matters
13
14### Should Consider
152. **[Issue]** (`file:line`)
16   - Details
17
18### Minor Notes
19- Observations
20
21## Tests
22[Coverage and quality assessment]
23
24## Complexity
25[Net impact on codebase complexity]

Numbering: Single sequence across all sections. Model attribution: [Codex + Claude], [Claude], etc.

Scope

In scope: Logic errors, missing error handling, test gaps, performance regressions, unnecessary complexity, duplication, incomplete implementations, project guideline violations.

Out of scope (linters handle): Formatting, import order, naming style, type annotations, docstring format.