Start with the list, not the code

You don't need to read every line. You need to know which files moved and whether that matches your request. In a terminal, inside your project:

git status
git diff --stat main

The first command lists what changed since the last commit. The second shows every file that differs from main, with the number of lines added and removed. On GitHub, the same information is in the Files changed tab of a pull request.

Ask yourself one question per file: does this belong to what I asked for? A contact form touches a form component, maybe an API route, maybe an email template. If you see a file about payments or user accounts in that list, that's where you look first.

Write your request down before you start

This sounds obvious, and almost nobody does it. Keep the request in a note, with the condition that makes it done. When the agent finishes, go through it line by line: done, not done, done differently. Then list what's there that you didn't ask for. That list is usually short, and it's the most useful thing you'll read all day.

Five changes to always open

  1. Database migrations. Files in folders like migrations or supabase/migrations change the structure of your data: new columns, renamed tables, deleted fields. They're easy to apply and harder to undo once real users have data in them.
  2. New packages. Look at package.json. A new line in dependencies means new code from someone else is now part of your app. Ask the agent why it was needed if it isn't obvious.
  3. Configuration and keys. Changes to .env.example, config files or anything with "key", "secret" or "token" in it. A key written directly in the code is a problem even if the app works.
  4. Deleted files and tests. Removed lines show in red. If a test was deleted or rewritten so it passes, find out why. Sometimes the old test was wrong. Sometimes the test was right and the code isn't.
  5. Sign-in and payments. Any change near authentication, permissions or billing deserves a slow read, even if it's a single line.

Ask the agent to explain itself, then check

A good habit at the end of each task is to ask: "List every file you changed and why, and anything you did that I didn't ask for." Agents are good at this summary. They're not always complete, so compare it with git diff --stat rather than taking it on trust. If a file is in the diff but not in the summary, open that one.

How to undo what you don't want

If the work is still on its own branch, nothing has reached your app yet. You can ask the agent to remove the part you don't want, or throw the branch away:

git switch main
git branch -D contact-form

To undo a single file before it's committed, use git restore path/to/file. If a change was already merged, git revert followed by the commit's identifier creates a new commit that cancels it, without rewriting history.

Make it a routine

Ten minutes per feature is enough once you know where to look. The point isn't to understand every line. It's to never be surprised by what's live.