> ## Documentation Index > Fetch the complete documentation index at: https://docs.cloudthinker.io/llms.txt > Use this file to discover all available pages before exploring further. # Review Workspace > Triage reviews, judge findings, apply fixes, and re-run reviews from the Reviews workspace inside CloudThinker Review posts its results to your merge requests and pull requests (MR/PRs), and mirrors every one of them at **Review → Reviews** inside CloudThinker — a workspace for triaging, reading, and acting on reviews without opening your Git provider. Every action here that has a comment twin links to its [mention command](/guide/code-review/mention-commands). ## Prerequisites * A repository connected through [Review Setup](/guide/code-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: | Tab | What it lists | | ------------------- | --------------------------------------------------------------------------------------------- | | **Needs attention** | Open MR/PRs that are not yet clean — still in review, failed, or carrying unresolved findings | | **Ready to merge** | Open MR/PRs reviewed clean | | **Merged** | Merged MR/PRs, kept as history | | **All** | Every MR/PR in the workspace | 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](/guide/glossary) (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](/guide/code-review/extensions), 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. 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. **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. **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 | Action | Where | Comment twin | | ---------------------- | ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | **Fix all with AI** | Header button | [`@cloudthinker-ai autofix`](/guide/code-review/mention-commands#how-autofix-works) — fixes unresolved findings and pushes to the source branch | | **Re-run review** | **⋯** menu | [`@cloudthinker-ai review`](/guide/code-review/mention-commands#commands) — restarts the review from the last reviewed commit | | **View review thread** | **⋯** menu | None — opens the agent's own review conversation | | **Open on provider** | **⋯** menu | None — jumps to the MR/PR on your Git provider | **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 Trigger the same actions from MR/PR comments on your provider Link issue trackers so reviews check ticket compliance Turn recurring resolved findings into repository rules Track review coverage, recurring findings, and trends