Branch Reviews

Branch reviews are the default fit for iterative review while a branch is still moving.

Best For

• rerunning review as a branch evolves
• validating fixes before publishing a PR
• tracking findings and outcomes over repeated review cycles

Typical Loop

1. Select the branch review context
2. Run review
3. Inspect findings and evidence
4. Mark findings addressed or dismissed as appropriate
5. Rerun after code changes

Example Walkthrough

A typical branch review session in Atlas looks like this:

1. Open a local project in the desktop app.
2. Let Atlas pick the current branch review context.
3. Run the review from the branch review surface or through an Atlas-connected agent.
4. Read the review summary, verdict, and finding list.
5. Open each finding to inspect the file anchors and reasoning.
6. Fix the code, or dismiss a finding only when there is a real rationale.
7. Rerun the branch review so the result matches the latest branch snapshot.

This is the best fit when you are still iterating and do not want to anchor the review to a GitHub PR yet.

Notes

• Branch review is the default current-review target in shared MCP resources and prompts
• Stale branch state should be rerun instead of trusted as final
• Action gating should follow review lifecycle truth rather than stale prior status