BuildGist

How do I review what Copilot changed?

Kayvan Zahiri ·

When GitHub Copilot coding agent finishes a task, the work shows up as commits on a branch, and, if you asked for one, as a pull request. The job is to know which files it touched, what it already validated in the session, and what is still risky, before anyone merges. GitHub's own review path, plus a 30-second claims check on BuildGist, gets you to the risky files first.

Check a PR or paste a session

A ready-made example opens on the same page if you just want to look.

Open the session, then the diff

GitHub's docs for Copilot coding agent, checked November 13, 2026, say you can follow a session from the agents panel or from Copilot's home. The session log shows the agent's reasoning, the tools it used, and the validation it ran. The session runs in an ephemeral environment, and can run tests and linters there before it pushes. Commits are authored by Copilot, with the person who started the session as a co-author. The commit message includes a link back to the session log, and the commits are signed and marked Verified.

After a session, click Diff to see the changes. You can also open the branch, named in the form copilot/BRANCH-NAME. Sessions do not create a pull request on their own unless you asked for one. When you are ready, create the pull request from the session.

You can continue the same session later from GitHub, the mobile app, or the Copilot CLI with /resume. Stopping a session keeps the commits it already pushed, so you can still review those.

Review the pull request itself

GitHub's docs on reviewing Copilot's output, checked November 13, 2026, say to review the pull request thoroughly before you merge. An approval on a pull request that Copilot opened does not count toward required reviews. If you want changes, comment with @copilot, or push commits of your own.

GitHub Actions do not run automatically when Copilot pushes. Inspect the changed files first, especially anything under .github/workflows/. Then use Approve and run workflows when you are ready for CI to run.

On a pull request Copilot created, Copilot Chat can use the session logs. GitHub's explore-pull-requests tutorial, checked November 13, 2026, shows asking what Copilot changed, what it validated, or for a summary of the agent session. That is useful context. It is not a substitute for reading the risky files.

Read in order of risk

Start where a small change has large consequences: sign-in, sessions and permissions; anything that deletes, overwrites or sends data; payments; new dependencies; configuration, including CI and new external services. Workflow files belong in that first pass, because Actions will not have run on Copilot's push until someone approves them. Docs last. For each important change, finish the sentence "Now a user can ...". If you cannot, keep reading that file.

What BuildGist adds

BuildGist answers a narrower question: did the agent do what it said, and what did it touch that it did not tell you about?

Paste a public GitHub pull request (or a git diff) at /try. The check compares the claims with the files in the diff and leads with three lists: files or tests the claims name that are not in the diff, changed files the claims never mention (risky ones first), and test claims with no test file or test run behind them. That comparison is plain matching. No AI writes it. Under it, BuildGist adds a plain-English explanation, written by AI, of what changed and what to check, and a short handoff you can copy into a fresh session.

BuildGist does not comment on bugs in the changed lines, suggest fixes, run your tests or prove the code is correct. The explanation can be wrong. The diff is still the thing you merge. Use GitHub's session log and your review of the pull request for what Copilot did and validated, BuildGist for the claims check, and your own reading of the risky files plus the tests before you merge.

The by-hand claims check is in how do I know what my coding agent actually changed before I merge? When the diff alone is enough is in BuildGist or the git diff. A fuller merge checklist is in how to review AI-generated code before you merge.

Questions

Does approving a Copilot pull request satisfy required reviews?

No. GitHub's docs say an approval on a pull request Copilot opened does not count toward required reviews. A person still has to review it.

Do GitHub Actions run when Copilot pushes?

Not automatically. Read the changed files first, especially workflow files, then use Approve and run workflows when you want CI to run.

Does BuildGist review Copilot's lines for bugs?

No. It checks what the run said it did against the files that changed, explains the change in plain English, and writes a handoff for a fresh session. The session log and your reading of the pull request are the review of the work itself.

Sources

What you need

Codex needs you to approve BuildGist once, in Codex. BuildGist shows the steps. Setup is in Getting started.

To explain a run, your computer sends BuildGist what that run needs, and BuildGist passes it to Anthropic. BuildGist does not keep this material. It does not send your whole repository, files the run did not change, or files named like secrets, such as .env files and keys. It keeps the explanation and short cited excerpts of changed code, at most 12 lines each. Secret masking is best-effort. Privacy has the full list.

Every account gets 7 days of BuildGist Pro free, with no card. The 7 days start at your first explanation or Continue handoff. Nobody is charged when the trial ends. After that, BuildGist Pro is $12 per month, plus any applicable tax shown at checkout. See pricing.

Try BuildGist Download for Mac

No Mac handy? Try it in your browser: paste a session or a git diff and see the explanation.

Apple silicon, macOS 12 or later. United States, 18 or older.

Related

Using another agent?

Questions: kayvanandre@gmail.com.