How do I review what Devin changed?
When Devin finishes a task in a connected repository, the work usually lands as a pull request. Your team's branch protections still apply, and a person reviews that pull request before it is merged. The job is to understand what Devin changed, what it flagged, and what is still risky, without rebuilding the session from scratch. Devin Review, plus a 30-second claims check on BuildGist, gets you to the risky files first.
A ready-made example opens on the same page if you just want to look.
Open Devin Review on the pull request
Devin Review's docs, checked November 13, 2026, say it groups related changes in a pull request, explains them alongside the diff, and flags potential bugs. On an open GitHub pull request or GitLab merge request in a repository your organization has connected, comment /devin review. You do not need to turn on auto-review for that. On a Devin session's pull request card, Analyze starts a review. If the card offers Analyze once, choose that for a single review; Analyze also turns on reviews for future pushes to this pull request.
You can also open Devin Review and pick a pull request you authored, one assigned to you, or one awaiting your review. For a github.com pull request, you can replace github.com with devinreview.com in the URL.
To hand Devin more work on a pull request, GitHub integration docs, checked November 13, 2026, say to comment /devin followed by what you want done, for example to fix a failing check and push a commit. If a Devin session is already working on that pull request, the comment goes to that session instead of starting a new one.
Read the grouped changes
The analysis starts with a short overview of the pull request's behavior and impact, then key changes in bullets when those help. Related edits are grouped into sections with explanations next to their diffs. Guide view groups related changes that way. File tree view shows ungrouped diffs with the file tree. You can hide whitespace-only changes and mark files Viewed.
Line counts in the pull request header, and on the Review list, leave out tests and generated code by default. Hover over a count for the breakdown, or click it to switch to the full count. On mobile, the review opens on Changes; switch to Bugs for bugs, flags and security findings.
When commits are pushed after the last review and no rule reviews them, a banner says the latest changes have not been reviewed. Review latest runs one more review of the current commit without turning auto-review on. In the review tab inside a Devin session, See changes shows what was pushed since the last review.
Devin's SDLC guidance, checked November 13, 2026, also describes Auto-Fix on an eligible pull request: the Devin session that opened it can fix a finding, dismiss it if no change is needed, or leave it for you to decide. That is a follow-up on findings. It is not a substitute for a person's review of 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. Docs last. Devin Review's grouping helps you see related edits together, but you still finish the sentence "Now a user can ..." for each important change. 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 Devin Review for the grouped read and for bugs it flags, 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 /devin review replace a human review?
No. It groups the changes, explains them next to the diff, and flags potential bugs. Your branch protections still apply, and a person still reviews the risky files and runs the tests before merge.
Does Analyze turn on reviews for later pushes?
Analyze on a session's pull request card also turns on reviews for future pushes to that pull request. If you want a single review, choose Analyze once when the card offers it.
Does BuildGist review Devin'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. Devin Review is the review of the lines and the flags.
Sources
- Devin Review, checked November 13, 2026.
- Devin GitHub integration (
/devinand/devin review), checked November 13, 2026. - How does Devin fit into my existing SDLC?, 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 Claude Code changed
- Review what Copilot changed
- Review what Windsurf changed
- Review what Gemini CLI changed
- Review what Cline changed
- Review what Aider changed
Using another agent?
- How to review what Claude Code changed
- 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 Cline changed
- How to review what Aider changed
Questions: kayvanandre@gmail.com.