Code Review in Atmos

Atmos Review helps you review changes before they leave your machine. You can read the diff, leave comments on exact lines, ask an agent to fix those comments, and repeat until the change is ready to push.

Overview

Each Review Session keeps its own comments and review rounds, so you can compare what changed after an agent fix.

1. Start a review session

1. Open the workspace with changes to review.
2. Open the right sidebar → Review tab.
3. Click New Review Session (or New Session in the session picker).
4. Atmos captures the current changes and creates a review session.

The session list supports Active, Closed, and Archived sessions.

2. Review in two ways

Both paths support multiple rounds of review and fixes.

2.1 Human diff review + agent fix

1. Under Changed Files, open a file to review its diff.
2. Hover a line and choose Add review comment.
3. Write the note and submit it.
4. Comments appear inline and under Comments in the sidebar.
5. In the actions bar, choose an agent and click Fix to send open comments to the Code Agent.
6. When the agent finishes, review the new version of the change.
7. Mark files Reviewed in the list or diff toolbar as you go.

Fix menu also offers Copy Prompt and Mark failed when needed.

2.2 Agent review with skills

1. In the Review tab, open the Fix menu chevron → Agent Review.
2. In Code Agent Review, pick a Review Skill (e.g. built-in reviewers or your custom skills).
3. Choose where the agent should run.
4. Start the review. The agent can leave comments and may write a review report.
5. Open the report and use Open session to jump back to the Review tab.

3. Test changes

After each fix round:

1. Re-read the diff for the current revision.
2. Run tests in the workspace terminal.
3. Confirm open comments are resolved or dismissed.

Use Summary in the Review sidebar when an agent creates a review report.

4. Commit or open a PR

When the snapshot looks good:

1. Commit from the Git view or terminal.
2. Open a draft or ready pull request from Atmos when GitHub is connected, or push and open a pull request from your normal Git workflow.
3. Use the Pull Requests and Actions tabs to inspect PR state and workflow results.
4. If a GitHub Actions job fails, use the Actions panel to hand a focused fix request to an agent.

Review sessions are local quality gates before remote review. They complement PR review and CI; they do not replace them.

Session management

From the session dropdown:

• Switch v1, v2, … revisions.
• Activate Session, Close Session, Archive Session, Rename.
• Refresh to reload sessions and comments.

The Code Review tab appears when a dedicated review agent is running.

Related

• Review Workflow — feature summary
• General Build Process — where review fits in the build loop
• Integrated Git Workflow