How to review AI-generated pull requests

By Arun Dass · Published 1 October 2026 · Updated 28 October 2026

Review an AI-generated pull request by checking it against the task first, then the tests, then the code. An agent’s pull request does not come with the author’s promise that they read and ran it, so ask for proof.

Why are agent pull requests harder to review?

When a person opens a pull request, you can assume they read their own change and ran it. With an agent, you cannot assume either. A diff also shows what changed, not what the software does.

Agents also open pull requests faster than people can read them, so review becomes the slow step.

What should you check, and in what order?

  1. Compare it with the task. Read the issue or the prompt first. Does the change solve that problem?
  2. Read the test changes first. A weakened or deleted test can make a broken change pass.
  3. Ask for proof it ran. Test output, a preview or a recording.
  4. Read the code for intent. Look at naming, edge cases and anything the agent decided that you would not have.
  5. Send failures back with steps to reproduce them.

GitHub’s own guidance on reviewing agent pull requests covers much of the same ground.

How do you keep review from becoming the bottleneck?

  • Review while the agent works, not after. A wrong turn is cheap to fix in the first few minutes.
  • Let automated checks handle formatting and known problems, so people can judge intent.
  • Keep changes small, with one task per pull request.
  • Ask the agent to say what it did not check.

How does Friday help with review?

In Friday every run ends in a change set you read before you keep it. You can leave notes on a line or a range and send them back to the agent, and see which lines the agent wrote and which you did.

Git is built in: stage by file or by hunk, commit, push, and open a pull request, stacked on another one if you are building in steps. On the task board, each finished task is checked before it counts as done: its tests run and another agent reviews it. That is a first pass. A person still reads the diff.

Friday runs on your own computer with no account, so the review happens in your copy of the repository, before anything reaches your remote.

Common questions

Should a person always review?

Automated checks help, but a person should decide whether the change solves the right problem before it ships.

Can one agent review another’s work?

Yes, as a first pass. In Friday, each finished task on the task board is checked by an agent that did not do it: its tests run and it reads the change. That is a first pass, and a person still makes the call.

How big should an agent’s pull request be?

Small enough to read in one sitting. One task per pull request is a good rule.

Run your next task in Friday.

Free and open source (MIT), on your own computer: the desktop app for macOS, Windows and Linux, or one command with Node.js 22.