@cloudthinker in any merge request or pull request comment on GitLab, GitHub, or Bitbucket to trigger commands — autofix findings, ask questions about the review, or get help.
Commands
| Command | What it does |
|---|---|
@cloudthinker help | Shows available commands as a comment |
@cloudthinker autofix | Fixes unresolved findings on the source branch |
@cloudthinker autofix stacked pr | Fixes findings on a new branch and pushes into the current MR/PR |
@cloudthinker <question> | Ask a free-form question about the code review |
How Autofix Works
Direct vs. Stacked PR
@cloudthinker autofix— Commits directly on the MR/PR’s source branch. Findings are marked resolved after fixing.@cloudthinker autofix stacked pr— Creates a new branch and pushes fixes into the current MR/PR’s source branch. Findings stay open for your review.
Free-form Questions
Ask anything about the code review by mentioning@cloudthinker followed by your question:
Thread-Aware Context
- Reply in a finding’s thread — The agent sees only that specific finding’s details (severity, file, line, suggested fix), giving you a focused answer.
- Top-level comment — The agent sees all unresolved findings from the review, giving you a broader perspective.
Supported Providers
| Provider | Mention Trigger | Thread Support |
|---|---|---|
| GitLab | @cloudthinker in MR note | Discussion threads |
| GitHub | @cloudthinker in PR comment | Review comment replies |
| Bitbucket | @cloudthinker in PR comment | Comment replies |
Tips
- One autofix at a time — Only one autofix can run per MR/PR. Wait for the current one to finish before starting another.
- Reuse conversation context — Free-form replies in the same thread reuse the conversation context, so follow-up questions build on previous answers.
- Push requires approval — Autofix pushes require human approval before changes go to the branch.
Related
Code Review Setup
Connect your repositories for automated code review
Convention Rules
Customize what CloudThinker checks in your code