Skip to main content
Ultra review is a deeper review you start on demand for one merge request or pull request (MR/PR). It hunts harder for the bugs that slip past a normal review, and comments only on the ones it has verified.
Ultra review is in beta, and it keeps improving with your feedback.

​
Why use Ultra review

Use it before you merge a change where a missed bug is expensive, such as a payment path, a data migration, or a concurrency fix. Ultra looks at the whole MR/PR from more angles and checks each serious issue before it posts. You get a few verified comments instead of a long list, so your team spends its time on fixes, not on sorting noise.

​
Prerequisites

  • A repository connected in Review setup on GitHub, GitLab, Bitbucket, or Azure DevOps.
  • Ultra review available in your workspace. To check, comment @cloudthinker-ai help on an MR/PR: when it’s available, the list includes review ultra.
  • You are the MR/PR author or an assignee.

​
Run an Ultra review

1

Open the MR/PR on your provider

Use an open MR/PR in a connected repository.
2

Post the command as a new comment

Put the command on its own line, with nothing after it:
@cloudthinker-ai ultra and @cloudthinker-ai ultra review work too.Success state: the bot replies CloudThinker Review Started.
3

Read the results

When the run finishes, a summary comment headed Ultra review (Beta) appears on the MR/PR.
  • Each inline comment is a Critical or High finding that Ultra verified, marked Verified.
  • Everything else worth a look sits in the summary’s Check by hand list, one line per issue, with its file and line.
Ultra runs once, on the MR/PR as it stands now. Your next push gets your normal review. If you push while Ultra runs, that push waits for it to finish. Ultra does more work than a normal review, so it can use more credits.

​
How it works

  1. Read the whole change. Ultra reviews every file in the MR/PR, even when an earlier review already covered the latest commit.
  2. A swarm of hunters. Many hunters search the change at once, each from its own angle: how it uses other code, how it handles edge-case inputs, and how it could break.
  3. Verifiers confirm. Verifiers check every bug the hunters find against your code, and drop the ones that don’t hold up.
  4. Keep the MR/PR quiet. Only verified Critical and High findings become comments. The rest goes into the summary, so nothing is lost.

​
Troubleshooting

Cause: Ultra review isn’t available in your workspace yet. Fix: contact CloudThinker support to join the beta.
Cause: you aren’t the MR/PR author or an assignee. Fix: ask the author to post the comment, or ask to be assigned to the MR/PR and comment again.
Cause: a review is in progress on this MR/PR, so CloudThinker doesn’t start a second one. Fix: wait for its summary comment, then post @cloudthinker-ai review ultra again.
Cause: the command wasn’t the whole line, for example @cloudthinker-ai review ultra please. Fix: post @cloudthinker-ai review ultra with nothing after it.
Cause: during the beta, Ultra starts only from a comment. A line in the MR/PR description doesn’t start it. Fix: post the command as a comment.
Check: the mention is plain text, not inside backticks, a code block, or a quote. Ultra isn’t available on AWS CodeCommit. For other causes, see Mention commands.

Mention commands

Re-run reviews, fix findings, and ask questions from MR/PR comments.

Review workspace

Settle findings, apply fixes, and merge from CloudThinker.