Prerequisites
- A repository connected through Review Setup
- Review view access to browse; resolving findings, applying fixes, and re-running reviews need Review edit access
Triage the Reviews list
Go to Review → Reviews. Four tabs bucket every MR/PR, each with a live count:
Each row shows the title, author, repository, MR/PR state, review verdict — Approved, Changes requested, In review, Review suggested, or Ignored — and how many findings (issues the review flagged for a human look) remain unresolved. Narrow the list by search text, repository, verdict, MR/PR state, review status, or author; your filters survive switching tabs.
Read a review
Open a row to see the review detail. The header carries the actions; the body splits into four tabs — Overview, Findings, Commits, and Changes — with a summary rail alongside.- Walkthrough — the reviewing agent’s narrative of what the change does and how it hangs together, on the Overview tab above the MR/PR description.
- Review summary — the verdict and finding counts, with a Rate this review row of 1–5 stars. Your rating is recorded against the review.
- Ticket compliance — when the review found a linked ticket through an extension, a verdict of Fully compliant, Partially compliant, or Not compliant against the ticket’s acceptance criteria, with the agent’s notes. The card appears only when a ticket was assessed.
Judge the findings
The Findings tab lists every finding as an expandable card with its severity, location, and suggested fix.1
Vote on accuracy
Mark a finding accurate with a thumbs-up, or inaccurate with a thumbs-down. An inaccurate vote asks for a required note explaining what the finding got wrong — that note tunes future reviews for the repository. Voting accurate later clears the note.
2
Apply or copy the fix
Apply fix commits the exact suggested change to the MR/PR source branch and marks the finding resolved. On providers where committing from CloudThinker is not available yet, the button is disabled — use Copy prompt to take the fix instruction to your own tools instead.
3
Settle the finding
Mark resolved records the finding as settled — the same status the agent writes when it verifies a fix — and Reopen undoes it. Both need Review edit access.Success state: settled findings dim in the list, and the review’s unresolved count drops on the Reviews list.
Inspect the code
- Commits — the MR/PR’s commit history grouped by day. Select a commit to open its changes.
- Changes — the full diff with a file tree and search. Files with large diffs open collapsed; click a file header to expand it. After selecting a commit, a banner shows the Changes panel is scoped to that one commit — View all changes returns to the full diff.
Ask about a review
Ask CloudThinker in the header opens a chat drawer beside the review, in a conversation scoped to this MR/PR — separate from the agent’s own review thread. From a finding card, Ask seeds the drawer with that finding’s details for a focused answer. The composer shows the scope as locked context chips — a repository chip with a branch picker, and finding chips labeled “Chat is scoped to this finding”. A locked chip cannot be removed, which is why the agent stays on this review instead of wandering off-scope.Re-run and fix from the header
Re-run review shows why it is unavailable — for example while a review is already running — and stays visible but disabled on merged MR/PRs. Users with view-only access see neither re-run nor autofix.
Next steps
Mention Commands
Trigger the same actions from MR/PR comments on your provider
Extensions
Link issue trackers so reviews check ticket compliance
Learnings
Turn recurring resolved findings into repository rules
Review Insights
Track review coverage, recurring findings, and trends