Reviewing a PR stack
A PR stack is a chain of dependent PRs. Each PR builds on the one below it. SimpleEdit opens the whole stack as one review in the Review Room, one layer per PR.
The AI in the Review Room helps you read. It writes an overview, suggests a reading order, looks for problems when you ask, and answers your questions. It never posts, approves or decides. Only comments you write or accept go to GitHub.
This guide covers your colleagues’ PRs and your agents’ PRs alike. When your own agent asked for the review, see also Reviewing your agent’s work.
1. Find the PR
Open Review queue in the sidebar (⌘2) and select a PR. The Review queue sorts your PRs and can open any PR you paste into it. See Triaging your Review queue.
2. Open the stack
Select a PR. The Review Room opens with every PR of its stack as a layer, from the bottom of the stack to the top. It shows one PR at a time under a layer bar. The Stack list at the top of the outline holds every PR, and you pick the one to read there. A PR that has been merged or closed since you opened the review stays in the list, muted, and says why it left.
For each layer, SimpleEdit shows only the changes of that PR, not the changes of the PRs below it. This is true even when GitHub’s “Files changed” tab mixes them.
3. Get oriented
Each layer has two optional buttons:
- ☰ Overview writes what the PR changes, why, and its impact. It also suggests a Reading order and a list of things to look into.
- ⚡ Deep review sends up to three Reviewers through the whole layer. Each reads the code at its head and reports problems. A Refuter then merges duplicate reports and tries to disprove each one. Each finding becomes a thread on its line and says how many Reviewers found it. With more than one Reviewer, the button’s menu runs only the first one or two. See Tuning Deep review.
Neither runs on its own. You choose when to use them.
If the repository has a REVIEW.md, the overview, Deep review and the Companion use it as a rubric.
If an agent asked for this review, its briefing shows first, labelled Author’s briefing. Its reading order drives the Reading list until you run ☰ Overview. See Reviewing your agent’s work.
4. Read the changes
- The outline on the right has three tabs: Discussion, Reading and Files. After ☰ Overview, follow the Reading list. It lists the steps of the suggested reading order. Discussion lists every thread and comment on the PR, and Files lists the files with their Viewed marks.
- Select Viewed on each file when you are done with it. A viewed file collapses. If the file changes after a push, the mark goes away and the file opens again.
- Files you would usually skim start folded, after the other files: tests, stories, lockfiles and generated files, vendored code, CI and tooling config, translations, assets, and deleted, renamed or binary files. Nothing is hidden. A folded file keeps its header, which says why it is folded, for example “test · test naming convention”. Select a header to open the file, or the Folded by default: … line to open them all. A step of the reading order always shows its files open.
- Use the picker in the layer bar to read one commit at a time, or All changes for the whole layer.
- After you submit, the next visit is a new round. See Reviewing the next round.
To choose which kinds of file start folded, open Settings → Review. The repo’s root .gitattributes also counts: files it marks linguist-generated, linguist-vendored or linguist-documentation count as generated, vendored or docs files. SimpleEdit reads that file from the PR’s base, so a PR can’t fold its own code. An agent that asks for a review can list files worth opening anyway; those start open with the author’s note.
SimpleEdit also folds changes in code that rules prove are mechanical, in JavaScript, TypeScript, Python, Go, Rust and Java: a hunk that only changes formatting, only changes comments, or only changes imports (an import added that the file now uses, or one removed that it no longer does). Inside an open file, such a hunk shows as one line, for example ”▸ imports only (+Context) · 4 lines · rule”. Select the line to open the hunk. A file where every hunk is mechanical folds as a whole, and the Folded by default: … line counts it as “mechanical”. A hunk that has a thread on one of its lines never folds, and a hunk you opened can be folded back to its summary. A doc comment on an exported declaration stays open, with a label, because it is documentation your users read. The check reads the file at the base and at the head. If it can’t read them in about three seconds, or the layer changes more than 150 files, the layer opens without mechanical folds, and stays that way until the next push. To turn this off, clear Fold mechanical code changes in Settings → Review.
A small local decision model can also reopen the rare folded file worth a look, such as a test of authentication. To set one up, open Settings → Default Model → Model checks and select Set up with an agent. That starts a session in your last-focused project window. The agent asks a few questions about what you prefer. For a model on your own machine, it checks your hardware, installs llama.cpp with the Kev-4B model in your terminal, and then proposes the settings. Nothing changes until you approve the card it shows: the URL and key apply only when you select Approve. See Driving SimpleEdit from your agent for the card. To remove the runner again, ask the agent. It lists the steps.
5. Discuss with threads
Findings, other reviewers’ GitHub comments and your own notes are all threads.
- Select a line, or + New thread.
- Pick who gets your message:
- Companion: a read-only agent that didn’t write the change and can read the code at the PR’s head. Select Ask. Use it to check a guess before you comment: “Is this function called anywhere else?” The conversation stays between you and the companion and is never posted.
- Author: the agent session that asked for this review. It is offered only while that session runs. Select Ask. Your question waits until the agent’s current turn ends, then goes to it as its next prompt. The author answers in the same thread.
- The PR: your comment for GitHub. Select Draft to turn what you typed into your comment. A thread has one draft, so this option disappears once the thread has one. On another reviewer’s GitHub comment it is labelled @name, and your draft is posted as a reply to them. On a local branch it is labelled Review.
- When the companion proposes a comment, select Use this text or Keep mine. To have the companion propose a comment from what you discussed, select Redraft from conversation.
- Select Done when a thread needs nothing more.
6. Submit
- Select Submit reviews….
- Set a verdict for each layer: Approve, Comment or Request changes.
- To keep a PR out of this submit, clear its Include box.
- Submit. SimpleEdit posts one review per PR and shows its progress, for example Posting · 3 comments. “This posts to GitHub as you.”
Only your drafts are posted, never the conversation behind them.
When GitHub sends back a comment you posted, it joins the thread you wrote it in, marked Posted. It doesn’t show up as a second thread.
If you already started a pending review on GitHub for a PR, SimpleEdit asks first: select Use it or Leave it out.
7. Come back later
Every review you started is in the Continue reviewing group of the Review queue, with its progress. Reopening a review resumes at the file you were on.
A review leaves the group once all its PRs are merged or closed, unless it still holds drafts that would post on Submit. Then its row says so (“merged · 2 drafts to post”). To take a row off the list yourself, hover it and click ×. The review and its drafts are kept, and the row comes back when you work in that review again.
8. Review the next round
When the author pushes after you submitted, the next visit is a new round that shows your feedback next to the changes that answer it. See Reviewing the next round.
On the phone
The Review tab of the phone companion opens the same Review Room. Threads, drafts and Viewed marks are shared between the desktop and the phone, and the phone folds the same files.