How to review an AI-generated pull request

By the AgentReceipt team · Updated 13 November 2026

A pull request written with an AI agent can look tidy and still hide problems. Reviewing it well means changing the order in which you look at things.

Step 1: find out what was asked

The diff shows what changed, not what was requested. Ask for the prompt, or read it from the session’s receipt. Everything else is judged against it.

Step 2: compare the files with the request

List the files in the diff and ask whether each one belongs. A change to an unrelated module is the clearest sign something went beyond the task.

Step 3: look at the risky parts first

Check tests, CI settings, new dependencies and anything touching authentication or payments before you read the rest. A receipt’s flags point to these.

Step 4: read the code

Only now read the logic itself. You will read it faster, because you know what it is meant to do and where the risk is.

agentreceipt show