How do I review what Claude Code changed?
To review what Claude Code changed, start with the file list and the patch. In the
session, run /diff. In the project folder, run git status and
git diff. Read the risky files first: sign-in, payments, permissions, secrets,
migrations and deploy config. Claude Code can also review the branch for correctness bugs
with /code-review. BuildGist does a different check: it compares what the run
said it did with the files that actually changed, and lists the risky unmentioned ones in
about 30 seconds.
A ready-made example opens on the same page if you just want to look.
See the patch first
Claude Code's docs, checked November 13, 2026, say /diff shows the edits
Claude has made so far, along with anything else you have not committed. In fullscreen
rendering it opens a panel beside the conversation. In the classic renderer it opens a
dialog above the prompt. A turn view shows one prompt's edits. A change Claude made through a shell command appears under Current, the working-tree view.
If you have left the session, or you want the same list in your own terminal:
git status
git diff --stat
git diff
git status includes files you had already changed before the run. Commit or
stash your own edits first if you want the list to be only this run. Files Claude created
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 Claude committed during
the run, also run git log --oneline -5 and git show. A fuller
walk-through is in
what did Claude Code change?
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. The patch, and a short claims check, get you to the risky files first.
Let Claude Code review the branch for bugs
/code-review (also /review) is Claude Code's own review,
described in its docs, checked November 13, 2026. You type it in the session. Claude reviews
the changes on your branch, looks for correctness bugs, and reports what it found.
With no target, the review covers the branch's commits ahead of its upstream, plus
uncommitted changes. If there is no upstream, it compares against main, or
against the previous commit. You can point it at a pull request, a path or a revision range.
--fix asks Claude to apply the findings to your working tree; edits go through your permission mode. --comment posts findings on a GitHub pull request
or GitLab merge request.
This is a review of the code itself. It is not a substitute for reading the risky files or running the tests. BuildGist does not run
/code-review.
If the run went the wrong way
Run /rewind, or press Esc twice when the prompt is empty, to open the rewind
menu (also /checkpoint or /undo). You can restore the code, the
conversation, or both, to an earlier prompt. Checkpoints are described in Claude Code's
checkpointing docs, checked November 13, 2026. Git remains the record you merge.
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 Claude Code session (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 /code-review for bugs in the lines, 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 /code-review replace reading the diff?
No. It reports correctness bugs in the branch's changes. You still read the risky files and run the tests. The diff is what you merge.
Does BuildGist review the code 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. Claude Code's
/code-review is the review of the lines.
Do I need to install anything?
No. /diff and /code-review are already in the Claude Code
session. The BuildGist check runs in your browser at buildgist.com/try. BuildGist for Mac
does the same for each meaningful run on your own machine, without pasting.
Sources
- Claude Code: Interactive
mode (
/diff), checked November 13, 2026. - Claude Code: Review locally with /code-review, checked November 13, 2026.
- Claude Code: Checkpointing
(
/rewind), checked November 13, 2026. - Git: git diff, checked November 13, 2026.
- BuildGist's try page and privacy page.
What you need
- A Mac with Apple silicon and macOS 12 or later.
- Claude Code, Cursor or Codex.
- A Git project. No commit, push, remote or GitHub repository is needed.
- A GitHub account, to sign in. BuildGist does not access your GitHub repositories.
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
- What did Claude Code change?
- Switch from Claude Code to Codex
- Understand code an agent wrote
- Hand off Claude Code to Cursor
- Review what Codex changed
- You’ve hit your session limit in Claude Code
- You’ve hit your usage limit in Codex
- Keep context across agents
- Review AI code before merging
- BuildGist or the git diff
- Claude Code session history
- Undo Claude Code changes
- BuildGist vs CLAUDE.md, AGENTS.md and HANDOFF.md
- Keep context from Claude Code to Cursor
- Resume an agent session in another tool
- BuildGist vs Conductor
- Codex context window full
- Undo Codex changes
- Cursor usage limit reached
- Review Cursor agent changes
- Codex session history location
- Your conversation is too long in Cursor
- One default coding agent, or two?
- Tools that summarize agent sessions
- Switch from Codex to Claude Code
- Move from Cursor to Claude Code
- Switch from GitHub Copilot to Claude Code
- Move from Windsurf to Cursor
- Switch from Gemini CLI to Claude Code
- Coding agent crashed mid-task
- Claude Code lost context after compacting
- What commands did the agent run?
- Turn an agent session into a PR description
- Which coding agents read AGENTS.md?
- Switch from Cursor to Codex
- Export a Claude Code conversation
- Keep the dead ends when you switch agents
- Write a handoff note for a fresh session
- Usage limit hit in the middle of a task
- Mac apps that explain agent runs
- Explain a Claude Code session
- What did my agent change before I merge?
- BuildGist vs an AI PR reviewer
- Review what Copilot changed
- Review what Windsurf changed
- Review what Gemini CLI changed
- Review what Devin changed
- Review what Cline changed
- Review what Aider changed
Using another agent?
- How to review Cursor agent changes
- How to review what Codex changed
- How to review what Copilot changed
- How to review what Windsurf changed
- How to review what Gemini CLI changed
- How to review what Devin changed
- How to review what Cline changed
- How to review what Aider changed
Questions: kayvanandre@gmail.com.