---
title: "doc0 PR reviews"
description: "Review AI-generated pull requests by their architecture, not line by line: see what your agent changed on a map of your whole repository, and what still calls it."
last_updated: "2026-10-14"
canonical_url: "https://www.doc0.dev/pr-reviews"
---

Your agent writes the code. You review the architecture.

# Review AI-generated pull requests on a map of your codebase.

> For dev teams that ship code written by AI agents: doc0 splits each pull request into a few changes, shows where each one sits in your codebase, and what still calls it.

[Book a 30-minute call](https://www.calendar0.app/book/alessandro-a/30min). 30 minutes. Bring a pull request.

## AI-generated pull requests are too big to read line by line.

Your agent is done. Now 451 lines in 27 files wait for your review, and nothing says where to start.

- The diff: 451 lines in 27 files.
- The map: 2 changes in 15 areas of your code.
- Look here first: 27 callers and 25 files depend on one change.

And it is not just this one. Across 22,000 developers, as their teams used more AI:

- +51% bigger pull requests
- 5× longer in review
- +31% pull requests merged with no review at all

Source: Faros AI, AI Engineering Report 2026.

You can’t read every line. You can see where each change lands.

## Connect your repository. doc0 maps all of it.

Functions and types become dots, grouped into areas by what calls what: 2,260 of them for aflsolutions/hono. Before you read a line of a pull request, you know where it lands.

## Open a pull request. It lights up on the map.

As you push, what your agent added, changed and removed lights up in place, next to the code that calls it. You see the shape of the change, so the architecture stays yours.

## Read it as a few changes, in order.

Each change in plain words, opened from one check on the pull request, with no bot comments. doc0 calls this view a lens. A change comes before the ones that depend on it.

## See what still depends on the code your agent touched.

Each change comes with the answers you would otherwise go and search for.

- Removed, but still called: With the file and line of the call.
- How far it reaches: Callers up to three calls away.
- Flows it runs in: The paths through your code that pass it.
- Docs that may need updating: doc0 pages written from its files.
- Pull requests it collides with: Open ones changing the same files.

## The map only draws calls it can prove: 99.9% precision on Next.js.

A call is drawn only when doc0 can show where it goes. A guess stays off the map.

99.9% of the 8,786 calls doc0 drew in Next.js that the TypeScript compiler could check, the compiler drew too (vercel/next.js at eeab6f4, packages/next/src, measured 2026-10-12).

- Time to draw a lens: 37 s, the median over 339 lenses in production.
- Bot comments: 0, One check on the pull request opens the lens.

## Bring a pull request. We’ll read it with you.

Pick a time: 30 minutes to connect a repository and read one of your pull requests with us. [Book a 30-minute call](https://www.calendar0.app/book/alessandro-a/30min).

## Questions before you book a call

### Does doc0 comment on my pull requests?

No. It adds one check, whose link opens the lens. Nothing is posted in the conversation.

### Which pull requests get a lens?

Those opened, reopened or pushed to, drafts included, up to a daily limit per workspace.

### How long does a lens take?

Usually under a minute after a push.

### Which languages does the lens read?

JavaScript, TypeScript, Python, Java, Kotlin, C#, Go, Rust, C, C++, PHP, Ruby and Swift.

### Does it replace code review?

No. It shows you where to look. You still read the code that matters and decide.

### Does doc0 keep my code?

Your repository is cloned, analyzed in memory, and deleted after processing. We keep file hashes, the indexed chunks we use to write and update your docs, and their embeddings, never a copy of your repository. Your code is never used for training. Generation, search and chat use third-party AI sub-processors; our full sub-processor list, with where each one processes data, is in the privacy policy. A lens reads the pull request's two commits the same way, and the diffs you open in it are read from GitHub and are not stored.

## Sitemap

See the full [sitemap](https://www.doc0.dev/llms.txt) for all pages, and the [home page](https://www.doc0.dev/).