eddieran Code Reviewer
Use this skill when the user wants a real engineering review instead of lint-style commentary.
Agent Compatibility
- Claude Code: supported
- Codex: supported
Inputs
- A diff, commit range, pull request, or a focused set of changed files
- Any failing test output, benchmark output, or bug report that motivated the review
Workflow
- Determine the exact review scope before commenting.
- Read surrounding code, not just the modified lines, until the behavior is clear.
- Prioritize findings by user impact:
- correctness and data loss
- security and trust boundaries
- concurrency and state corruption
- performance regressions
- migration and rollout risk
- Call out missing coverage whenever behavior changed without tests.
- Distinguish between confirmed defects, plausible risks, and open questions.
Output Contract
- Findings first, ordered by severity.
- Each finding includes:
- a short title
- affected file paths
- the concrete failure mode
- why the issue matters in production
- the smallest safe fix
- If no material findings remain, say so explicitly and mention residual testing gaps.
Guardrails
- Do not flood the user with style nits.
- Do not speculate without a code path or failure scenario.
- Do not propose broad rewrites unless the current design is unsound.