Skip to main content
Mention @cloudthinker-ai in a merge request or pull request (MR/PR) comment to re-run a review, fix its findings, or ask about the change, all without leaving your Git provider. A finding is one issue the review flagged for a human to look at.

​
Prerequisites

  • An open MR/PR in a repository connected in Review setup.
  • Comment access on that MR/PR in your Git provider.

​
Commands

Write the command as plain text on its own line in a comment. Type @cloudthinker-ai exactly, whatever your bot user is called. Your provider’s autocomplete may not suggest it, and that’s fine. review and review ultra must be the whole line. @cloudthinker-ai review this carefully is treated as a question, not a command. A mention inside a code block, inline code, or a quoted reply is also never run as a command.

​
Run a command

1

Open the MR/PR on your provider

Use the MR/PR on GitHub, GitLab, Bitbucket, Azure DevOps, or AWS CodeCommit that CloudThinker reviewed.
2

Post the command as a new comment

For example, to re-run a review that stopped part way:
Success state: the bot replies CloudThinker Review Started. When the run finishes, a new review summary comment appears on the MR/PR.
If a review stops before its summary, the bot edits its progress comment to CloudThinker Review Did Not Finish. Findings it already posted stay valid. Comment @cloudthinker-ai review to continue from the last reviewed commit. On AWS CodeCommit, push a new commit to the source branch instead.

​
Ask a question

Mention the bot followed by your question:
Where you ask changes what the agent focuses on: Follow-up questions in the same thread build on earlier answers.

​
Push back on a finding

If you’re the MR/PR author or an assignee and you think a finding is wrong, reply in that finding’s thread. No mention is needed. Explain why, for example:
CloudThinker re-checks the finding against the current code and your reply, then settles it one of three ways: Pushing back works once the review has finished, on every provider except AWS CodeCommit. Other people can still ask about a finding by mentioning the bot, but their reply doesn’t settle it.

​
Fix findings with autofix

Pick how you want the fixes delivered:
1

Post the command as a top-level comment

2

Wait for the fix run

CloudThinker reads each unresolved finding, whether or not it has a suggested fix, changes the code, commits, and pushes. Only one autofix runs per MR/PR at a time. A second request while one runs doesn’t start another.CloudThinker doesn’t run your tests. It skips a finding that needs an architectural decision or has no clear fix. The fix run is an agent run and uses credits.Success state: a commit titled fix: autofix findings from code review of ... appears on your source branch, or a new MR/PR opens that targets it. The commit message lists each fix under Fixed: and each skipped finding, with its reason, under Skipped:.
On GitHub and GitLab you can also type @cloudthinker-ai autofix as a reply inside one finding’s thread. CloudThinker then fixes only that finding.
@cloudthinker-ai autofix pushes to your source branch without a separate approval step. CloudThinker doesn’t limit it to the MR/PR author, and there’s no CloudThinker setting that does: anyone who can comment can run it. On a widely shared repository, limit who can comment in your provider, and use autofix stacked when you want to read the changes first.

​
Skip a review

Put this anywhere in the MR/PR description to stop CloudThinker reviewing that MR/PR:
It’s case-sensitive. CloudThinker reads the description on every new event, so adding the marker skips reviews from the next push, and removing it lets the next push be reviewed. A review that’s already running finishes; to end it, use Stop review in the Review workspace. To skip whole groups of MR/PRs, such as bot dependency bumps, use repository filters in Review setup instead.

​
Run an Ultra review

Ultra review (beta) is a deeper review of the whole MR/PR that comments only on verified bugs. The MR/PR author or an assignee starts it with @cloudthinker-ai review ultra. See Ultra review for what it finds, who can run it, and what to do when it is off.

​
Provider support

  1. Only the MR/PR author’s or an assignee’s replies in a finding’s thread are read. Anyone else’s thread reply, a question included, gets no answer; they can ask in a top-level comment instead.
  2. Top-level comments only, not inside a finding’s thread.
review covers review ultra too. On AWS CodeCommit, automatic reviews still run on every new PR and on every push to its source branch. The review and autofix comment commands aren’t supported there, so push a new commit to review a CodeCommit PR again. A command your provider doesn’t support is ignored without a reply.

​
Troubleshooting

Check:
  • The mention is plain text, not inside backticks, a code block, or a quote.
  • Your provider supports the command in the table above.
  • On Azure DevOps, the Pull request commented on service hook exists with Resource version set to 2.0, as described in Provider authentication.
  • Your provider’s webhook delivery history shows the comment event was delivered and accepted.
Cause: review and review ultra must be the whole line. Fix: post @cloudthinker-ai review with nothing after it.
Cause: only the MR/PR author or an assignee can start Ultra, and only while Ultra is available in your workspace. Fix: see Ultra review troubleshooting.
Cause: only the MR/PR author or an assignee can settle a finding by replying, and only after the review has finished. Fix: ask the author to reply, or mark it resolved in the Review workspace.

​
Next steps

Review workspace

Run the same actions, plus merge, from inside CloudThinker.

Learnings

See the rules CloudThinker learns from your team’s settled findings.