> ## 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

> Get an AI review on every pull or merge request, with findings posted as comments in GitHub, GitLab, Bitbucket, Azure DevOps or CodeCommit.

**Nothing breaks in production.**

Review is the Frontier Investigation Agent for code changes: an AI reviewer for your pull requests (PRs) and merge requests (MRs). When someone opens one, CloudThinker reads the change, posts a summary comment and inline findings on it, and checks the fix when you push again.

A linter matches patterns. Review reads what the change is trying to do: the diff, the linked ticket, your team's convention files and, if you keep one, a `BUSINESS.md` that describes the rules your product must keep. That lets it flag a broken business rule or a risky migration, not only a style slip.

## How it works

![When a PR or MR opens, the Git provider sends CloudThinker an event; CloudThinker gathers the diff, linked ticket and repository files, runs the review, and posts a summary and inline comments on the PR, and each new push gets an incremental review.](https://mintcdn.com/cloudthinker/IOnNsZPtwT4C7tHY/images/code-review/diagram-code-review-light.svg?fit=max\&auto=format\&n=IOnNsZPtwT4C7tHY\&q=85\&s=93aea9f03f5da250e77af150c80c10e6)

Every PR or MR gets a review posted back on it, and each new push gets an incremental review.

1. **A PR or MR opens.** You connect your Git provider and pick repositories once, and after that your provider sends CloudThinker an event whenever a PR or MR opens, with nobody starting a review. Draft PRs and MRs are skipped until they're marked ready for review.
2. **CloudThinker gathers context.** It checks out the change and reads the diff, a ticket linked from the description (Jira, Linear, Backlog or a provider issue, once you add an [extension](https://docs.cloudthinker.io/guide/code-review/extensions.md)), and the files listed in [What Review reads](#what-review-reads).
3. **The review runs.** Depth depends on the workspace [review mode](https://docs.cloudthinker.io/guide/code-review/setup.md#choose-a-review-mode): **Fast**, **Auto** or **Advanced**. Each review uses credits; see [usage and credits](https://docs.cloudthinker.io/guide/billing/usage.md).
4. **Findings land on the PR.** You get one summary comment plus inline comments. Each finding has a severity (Critical, High, Medium or Low) and a suggested fix.
5. **New pushes get an incremental review.** Only the commits pushed since the last review are read, and the review checks whether earlier findings were fixed.

The most severe unresolved finding sets the review's verdict, and a run that never finished or was skipped gets a status of its own instead. The verdict is CloudThinker's label on the change, and your provider's branch rules still decide whether it can merge. See [verdicts](https://docs.cloudthinker.io/guide/code-review/review-workspace.md#triage-the-reviews-list) for all seven and what each one asks of you.

> [!NOTE]
>
> CloudThinker keeps its own copy of each selected repository to read it, and deletes those copies when you click **Remove setup**. Secrets in tool output are replaced with placeholders before the model sees them; see [data protection](https://docs.cloudthinker.io/guide/security/data-protection.md).

Changed test files, fixtures and test data, snapshots, generated code, Storybook stories, prototypes, HTML under `docs/` and vendored Jsonnet aren't reviewed: no finding is ever placed in one.

> [accordion] Full list of skipped path patterns
>
> ```text theme={null}
> **/test_*.py              **/conftest.py              **/*_test.go
> **/src/test/java/**/*.java                            **/src/test/**/*.{kt,kts}
> **/*.test.{js,jsx,ts,tsx} **/*.spec.{js,jsx,ts,tsx}   **/__tests__/**
> **/test/**/*_test.py      **/tests/**/*_test.py       **/*_test.py
> **/*_spec.rb              **/spec/**/*_spec.rb        **/*Test.java
> **/*Tests.java            **/*_test.rs                **/oh_modules/**
> **/*.test.ets             **/test/**/*.jl             **/test/**/*.hs
> **/*Spec.hs               **/test/**/*.lhs            **/*Spec.lhs
> **/tests/**/*.nim         **/tests/**/*.R             **/__snapshots__/**
> **/*.snap                 **/testdata/**              **/fixtures/**
> **/.ipynb_checkpoints/**  **/*.generated.*            **/*.gen.go
> **/*.pb.go                **/*.pb.cc                  **/*.pb.h
> **/*Test.swift            **/*Tests.swift             **/Tests/**/*.swift
> **/tests/**/*.elm         **/vendor/**/*.{jsonnet,libsonnet}
> **/test/**/*.zig          **/*_test.zig               **/kitex_gen/**/*.go
> **/*.capnp.h              **/*.capnp.go               **/*.capnp.ts
> **/*_capnp.rs             **/*_capnp.py               **/test/**/*.ml
> **/tb_*.{v,sv,vhd,vhdl}   **/*_tb.{v,sv,vhd,vhdl}     lib/**/*.sol
> **/*.t.sol                **/test/**/*.sol            **/tests/**/*.sol
> **/test/**/*.vy           **/tests/**/*.vy            **/*.stories.{js,jsx,ts,tsx,mdx}
> **/prototypes/**          **/docs/**/*.html
> ```

Matching is by file path only, against this built-in list that you can't add to. For the paths this catches by surprise, see [findings are wrong or noisy](https://docs.cloudthinker.io/guide/code-review/troubleshooting.md#findings-are-wrong-or-noisy).

## What Review reads

Besides the diff, Review reads your team's own knowledge. All of it is optional, and it makes every review sharper over time.

| File | Where it goes | What it does |
| - | - | - |
| [`BUSINESS.md`](https://docs.cloudthinker.io/guide/code-review/business-flow) | Repository root, on the target branch | Describes your product's modules and the rules (invariants) they must keep. Business flow findings come from it. Read whenever it exists: it doesn't depend on **Repository conventions** |
| Convention files | `AGENTS.md`, `CLAUDE.md`, `CONVENTIONS.md` and the rule files of coding agents such as Cursor or Copilot, in the repository root or any folder | Coding conventions Review follows, when **Repository conventions** is on. [Every path it recognizes](https://docs.cloudthinker.io/guide/code-review/learnings.md#add-your-own-convention-files) |
| [Learnings](https://docs.cloudthinker.io/guide/code-review/learnings.md) | Kept by CloudThinker for each repository, no file needed | Rules CloudThinker learns from the findings your team resolved. Review applies them to every new review, so the same mistake gets caught the next time |

You write `BUSINESS.md` by hand in a short, fixed format: see [Business flow checks](https://docs.cloudthinker.io/guide/code-review/business-flow.md). If the file doesn't parse, the review still runs without it.

## What it checks

Each finding carries one category.

| Category | What it catches | Example |
| - | - | - |
| Security | Injection, exposed secrets, unsafe auth or permissions | A query built from request input without parameters |
| Correctness | Logic errors, null handling, race conditions | A lost update when two requests write the same row |
| Performance | Slow queries, N+1 loops, blocking calls | A full table scan inside a request handler |
| Pattern | Breaks a convention your repository already follows | A new handler that skips the shared error wrapper |
| Deploy, migration, backward compatibility | Changes that break a rollout or existing clients | A migration that drops a column the current release still reads |
| Test gap | Changed behavior that no test covers | A new error path with no test, in a PR that adds none |
| Business flow | A change that breaks a rule in your `BUSINESS.md` | Code that lets a trial account use a feature an invariant reserves for paid plans |

## What you can do

| Capability | What you get | Learn more |
| - | - | - |
| Automatic review | A summary and inline findings on every new PR or MR | [Set up Review](https://docs.cloudthinker.io/guide/code-review/setup.md) |
| Follow a walkthrough | One pull request that would break production: the finding, how you check it, and the fix before the merge | [Catch a risky pull request with Review](https://docs.cloudthinker.io/guide/use-cases/review-risky-pull-request.md) |
| Overview dashboard | Find changes waiting on you and check review activity | [Review Dashboard](https://docs.cloudthinker.io/guide/code-review/dashboard.md) |
| Codebase Atlas | See what your team merged, where it landed and what needs attention | [Codebase Atlas](https://docs.cloudthinker.io/guide/code-review/codebase-atlas.md) |
| Ultra review | A deeper review that posts only verified bugs worth fixing, started with one comment | [Ultra review](https://docs.cloudthinker.io/guide/code-review/ultra-review.md) |
| UI Review: Loupe | Screenshots of the pages a change touches, checked in your running app before merge | [UI Review: Loupe](https://docs.cloudthinker.io/guide/code-review/loupe.md) |
| Business flow checks | Findings when a change breaks a pricing, entitlement or money rule you describe | [Business flow checks](https://docs.cloudthinker.io/guide/code-review/business-flow.md) |
| Personalization | Set summary sections, tone and language for your team | [Review Personalization](https://docs.cloudthinker.io/guide/code-review/customizations.md) |
| Repository management | Control Review, Atlas mapping and Learnings per repository | [Manage Review Repositories](https://docs.cloudthinker.io/guide/code-review/repository-management.md) |
| Review workspace | Every reviewed change, its findings and status, in CloudThinker | [Review workspace](https://docs.cloudthinker.io/guide/code-review/review-workspace.md) |
| Mention commands | Ask a question, re-run a review or fix findings with `@cloudthinker-ai` in a PR comment | [Mention commands](https://docs.cloudthinker.io/guide/code-review/mention-commands.md) |
| Learnings | Recurring patterns from resolved findings, applied to future reviews | [Learnings](https://docs.cloudthinker.io/guide/code-review/learnings.md) |
| Pipeline analysis | An explanation and suggested fix for each failed CI run | [Pipeline Analysis](https://docs.cloudthinker.io/guide/code-review/pipelines.md) |
| Auto-resolve conflicts | A follow-up MR/PR that resolves merge conflicts on an open MR/PR. Not on Azure DevOps | [Auto-resolve conflicts](https://docs.cloudthinker.io/guide/code-review/conflict-resolution.md) |
| Release Risk | One ship-or-block verdict on every release tag, shared with the team, and a deploy that waits on blockers | [Release Risk](https://docs.cloudthinker.io/guide/code-review/releases.md) |
| Insights | Which finding categories hit your team, and how fast they get fixed | [Insights](https://docs.cloudthinker.io/guide/code-review/analytics.md) |
| Troubleshooting | Why a review didn't post, stopped or was skipped, with the cause, the check and the fix | [Review troubleshooting](https://docs.cloudthinker.io/guide/code-review/troubleshooting.md) |

## Supported providers

GitHub, GitLab (GitLab.com or self-hosted), Bitbucket Cloud, Azure DevOps and AWS CodeCommit. See [provider authentication](https://docs.cloudthinker.io/guide/code-review/provider-auth.md) for what each one needs. Check these limits before you plan a rollout:

* **One provider and one Azure DevOps project per workspace.** A second provider, or repositories in a second Azure DevOps project, need their own workspace.
* **Self-hosted GitLab is the only instance URL you can enter.** GitHub Enterprise Server and Bitbucket Data Center aren't options, and a CodeCommit connection covers one AWS account and region.

Automatic reviews run on all five providers. The actions on top of them don't:

* Comment commands with `@cloudthinker-ai` differ by provider, and AWS CodeCommit takes top-level questions only. See [provider support](https://docs.cloudthinker.io/guide/code-review/mention-commands.md#provider-support).
* **Apply fix** is listed per provider in [Work the findings](https://docs.cloudthinker.io/guide/code-review/review-workspace.md#work-the-findings); **Fix all findings** and **Merge** in [Re-run, fix, and merge](https://docs.cloudthinker.io/guide/code-review/review-workspace.md#re-run-fix-and-merge).
* [Auto-resolve conflicts](https://docs.cloudthinker.io/guide/code-review/conflict-resolution.md) works on every provider except Azure DevOps.

Two pieces of text look alike but go in different places: `@cloudthinker-ai` in a comment asks a question, a re-review or a fix, while `@cloudthinker:ignore` in the description [skips the review](https://docs.cloudthinker.io/guide/code-review/mention-commands.md#skip-a-review) on that one change. See [mention commands](https://docs.cloudthinker.io/guide/code-review/mention-commands.md).

## Get started

> [card] [Set up Review](https://docs.cloudthinker.io/guide/code-review/setup.md)
>
> Connect a provider, pick repositories and get your first review.

> [card] [Provider authentication](https://docs.cloudthinker.io/guide/code-review/provider-auth.md)
>
> Tokens, scopes and webhooks for each Git provider.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.