Some options for reviewing AI-generated pull requests

As you may have heard, AI is kind of a big deal now. Many of us use agents to ship more code, faster and better.

One side effect of this is PRs are bigger. Instead of a few hundred lines, they’re thousands of lines (or even tens or hundreds of thousands). Far more than we can review like we used to, understanding what every line is doing.

How should code review change for this new reality? I’m not sure yet, but here’s some ideas.

YOLO. Why bother? CI is green and the agent is confident. Just ship it.

The catch: while fine for side projects and prototypes, for customer-facing work we need to see the code to be sure of performance, security, accessibility, etc.

Automated reviewers leaving summaries or comments. Or even have an agent use an MCP from your machine, so it can see how changes fit into the overall codebase and architecture.

The catch: while genuinely useful, this still relies on the judgement of an agent. And it’s indirect. You’re talking about the code instead of reviewing it.

Force developers to break their work up into a chain of small PRs. The idea is each one is easy to understand on its own and can be merged safely. Tools like Graphite make this easy to do.

The catch: it can work for some developers, but often the individual stacks aren’t useful on their own. For example, first some scaffolding, followed up by some dependencies installed, and then a few thousand lines of the actual implementation. And changing one of the stacks can mean rebase-hell.

Have AI analyze a diff and dynamically slice into smaller, logical chunks for review. This has the same conceptual benefit of Stacked PRs, but executed only when needed. PR authors don’t need to structure their commits in a certain way to make sense.

A few products have done this, and I’ve built a demo at https://prismstudio.dev/sandbox/layers using mock data. Give it a whirl and see what you think. One day I might build it for real.

You can also signup at https://prismstudio.dev for the existing Github/Gitlab inbox and review UI.

What do you think, did I miss any options or get something wrong?