BuildGist

How do I review what Gemini CLI changed?

Kayvan Zahiri ·

Gemini CLI shows you the patch before it writes the file. The first review, then, is the proposed diff: accept it, reject it, or edit it. After a change is applied, Git is how you see the full set, and /rewind is how you step back. Confirming each diff as you go, then 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.

Confirm the proposed diff before it is applied

Gemini CLI's file-management docs, checked November 13, 2026, say that before any file is modified, Gemini CLI presents a unified diff of the proposed changes. Red lines are code that will be removed. Green lines are code that will be added. Press y to apply the change to your local files, or n to cancel and refine your prompt.

With the Gemini CLI Companion extension, the same proposal can open in your editor's native diff viewer. The IDE integration docs, checked November 13, 2026, say you can accept a diff with the checkmark in the title bar, by saving the file, with Gemini CLI: Accept Diff, or by answering yes in the CLI. You can reject it with the x, by closing the tab, with Gemini CLI: Close Diff Editor, or by answering no. You can edit the suggestion in the diff view before you accept it. If you choose Allow for this session, later changes are auto-accepted and no longer appear as IDE diffs, so take another pass with Git before you commit.

See what was already applied

Once you have accepted edits, the working tree holds them:

git status
git diff --stat
git diff

git status includes files you had already changed. Commit or stash your own edits first if you want the list to be only this run. New files show up as untracked until they are added. git diff is what is not staged yet. git diff HEAD is everything since the last commit.

If the run went the wrong way

The Rewind docs, checked November 13, 2026, say /rewind (or press Esc twice) opens a list of earlier interactions. As you move through the list you see a preview of the user prompt and, when files changed, how many were touched at that step. After you pick a point, you can rewind the conversation and revert the code, rewind only the conversation, or revert only the files. If no code changed since that point, the revert options are hidden.

Rewind is destructive for the current session history, and it can change files, so use it with care. It only reverts file changes made by the AI's edit tools. It does not undo edits you made yourself, or changes made through the shell tool. If you revert the code and keep the conversation, you may need to tell the model that the files have changed.

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. Docs last. A one-line auth-check change can matter more than a long rewrite of a readme. 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. Confirm each proposal in the unified diff, use BuildGist for the claims check on what was applied, and read 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 pressing y mean I have reviewed the change?

It means you accepted that one proposed diff. You still need a pass over the full working tree, the risky files, and the tests, especially if you allowed changes for the rest of the session.

Does /rewind undo edits I typed myself?

No. The Rewind docs say it only reverts file changes made by the AI's edit tools, not manual edits or changes made through the shell tool. Git remains the record you merge.

Does BuildGist review the 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 unified diff you accepted, and your reading of the risky files, are the review of the lines.

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.