Claude Code just shipped a feature that fixes its own code review.

You run /code-review --fix and it applies the changes straight to your working tree. No copy-paste, no "accept this suggestion" loop. It just does it.

This saves real time. It's also where a lot of people are about to get burned.

Because the job has quietly changed. A year ago you were writing the code. Now you're reviewing it. And the better these tools get, the more tempting it is to stop reviewing and just accept whatever lands.

That's the actual risk. Not that the AI is wrong. It's that you stop checking whether it's wrong.

There's a line I keep coming back to: you can outsource your thinking, but you can never outsource your understanding. When your name is on the commit, you take the credit when it ships clean. You also own it when it breaks at 2am.

So here's the filter I use with any auto-fix, code or content:

If it's low stakes and reversible, let it run. Formatting, a rename, a test stub. Who cares.

If it touches logic, money, or anything a user sees, it drafts and I review. Every time. The auto-fix gets me to a reviewable diff faster. It doesn't get me out of reading the diff.

That's the whole game now. Reading better, not shipping blind.

Try it this week. Next time you accept an AI change without reading it, stop and ask whether you actually understand what changed. If you can't explain it, you don't own it yet.

What's one thing you let AI run fully hands-off, and one thing you'll never stop reviewing? Curious where people draw the line.

0 comments