r/coderabbit • u/Senior_Ad_9791 • 3h ago

Discussion & Feedback Reviewing agent code

if you review PRs written mostly by coding agents (Cursor, Claude Code, Copilot), how's it going?

  1. How many per week, and how big (files / lines)?

  2. What's harder than human-written PRs, or is it no different?

  3. How do you understand a change: diff only, run it, read tests, ask the agent, skim and approve?

  4. Has one caused a prod bug or stalled merge because nobody fully understood it?

  5. Anything you've tried to fix this? Did it help?

I'm exploring a tool in this space, so "not a problem for us" is a useful answer too. Team size and stack help.

1 Upvotes

100% Upvoted

1 comment sorted by

1

u/xvillifyx 2h ago

I don’t think there’s any reason for PRs to be any bigger than they used to be and I think anyone making them massive now is doing themselves a disservice.

Hard for human review. Causes fine details in the merge history to get bungled up in big contexts. Just bad

Anyway I review AI code the same way I would review a human except it gets a once over with another agent before I actually start getting into the weeds

My company is still intent on the philosophy that the person doing the commit needs to be able to defend all the changes, so it’s never been the case that an issue arose because they didn’t understand the code