Review changes and pull requests
Inspect the diff and check the evidence before shipping.
A completed turn is a starting point for review. Compare the result with the original request and any later decisions before merging or releasing it.
Read the visual explanation
Inspect the changed files, compare the diff to the request, and read which checks ran before opening the pull request for your normal review.
Inspect the changed files
- Open the session's changes or files panel.
- Confirm the repository and branch context, especially for multi-repository work.
- Open the files relevant to the requested behavior.
- Read additions and removals together. Look for unrelated edits, missing edge cases, and changes to public interfaces.
- Compare the diff with the acceptance criteria and the agent's summary.
Ask for a focused correction in the same session when the result needs another pass. State the precise issue and expected behavior so the next turn retains the review context.
Review checks honestly
Read which checks ran, their outcomes, and any prerequisites that prevented a check. A skipped check supplies no passing evidence. A test that exercises a helper may not verify the complete user flow.
For UI changes, inspect the preview at relevant widths. For generated files, inspect outputs. Run additional checks your team requires.
Open the pull request
When the agent publishes a PR, follow its link from the session or output. Confirm its base branch, scope, description, and current diff. A reported local check and an independent code review answer different questions; use both where your team requires them.
A PR link does not mean the PR is merged. Ask for a PR explicitly when it is part of the delivery request, and verify the merge in your normal source-control workflow. Uno does not make a review requirement disappear because an agent wrote the change.