Most teams think of AI code review as something that happens after a PR is opened.
That’s too late.
The Claude Code team at Anthropic does something I think more teams should straight up steal:
- Claudey A (my pet name for Claude) writes the plan.
- Claudey B reviews it as a “staff engineer” — skeptical, looking for edge cases, questioning assumptions.
Two agents. Different roles. The writer doesn’t review its own work.
Think about why this matters. When you let the same agent that wrote the code also validate it, you’re literally asking the student to grade their own test. Of course it looks correct — it was designed to look correct.
📝 The key insight that changed how I work: When it’s time to review, I kill my session and start a brand new one — fresh context window, zero contamination from the implementation. It’s like getting a second opinion from a completely different engineer. Issues that used to show up days later in PR review now get caught before a PR even exists.
Layer it: AI review during dev. AI review at the PR level via CI. Humans for judgment calls.
Don’t let the agent grade its own homework, unless you’re spidey. 🕷️
Related: Stop Reading Every Line of Code → — the full essay on rethinking code review for the AI era.
답글 남기기