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

# Mention Commands

> Interact with CloudThinker directly from MR/PR comments

Mention `@cloudthinker-ai` in any merge request or pull request comment to trigger commands — autofix findings, ask questions about the review, or get help.

<Warning>
  Mention commands are currently available on **GitLab** and **GitHub** only. Bitbucket and Azure DevOps support is coming soon.
</Warning>

***

## Commands

| Command                               | What it does                                                     |
| ------------------------------------- | ---------------------------------------------------------------- |
| `@cloudthinker-ai help`               | Shows available commands as a comment                            |
| `@cloudthinker-ai autofix`            | Fixes unresolved findings on the source branch                   |
| `@cloudthinker-ai autofix stacked pr` | Fixes findings on a new branch and pushes into the current MR/PR |
| `@cloudthinker-ai <question>`         | Ask a free-form question about the code review                   |

***

## How Autofix Works

<Steps>
  <Step title="Comment">
    Post `@cloudthinker-ai autofix` (or `@cloudthinker-ai autofix stacked pr`) as a comment on the MR/PR
  </Step>

  <Step title="Analyze">
    CloudThinker picks up all unresolved findings from the review
  </Step>

  <Step title="Fix">
    An agent implements fixes for each finding, following your codebase conventions
  </Step>

  <Step title="Push">
    Changes are committed and pushed to the branch
  </Step>
</Steps>

### Direct vs. Stacked PR

* **`@cloudthinker-ai autofix`** — Commits directly on the MR/PR's source branch. Findings are marked resolved after fixing.
* **`@cloudthinker-ai 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-ai` followed by your question:

```
@cloudthinker-ai why was this function flagged as a security risk?
@cloudthinker-ai can you explain the performance impact of this change?
@cloudthinker-ai what's the best way to refactor this?
```

### 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         | Status      |
| ------------ | -------------------------------- | ---------------------- | ----------- |
| GitLab       | `@cloudthinker-ai` in MR note    | Discussion threads     | Available   |
| GitHub       | `@cloudthinker-ai` in PR comment | Review comment replies | Available   |
| Bitbucket    | —                                | —                      | Coming soon |
| Azure DevOps | —                                | —                      | Coming soon |

***

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

<CardGroup cols={2}>
  <Card title="Code Review Setup" icon="gear" href="/guide/code-review/setup">
    Connect your repositories for automated code review
  </Card>

  <Card title="Convention Rules" icon="book" href="/guide/code-review/convention-rules">
    Customize what CloudThinker checks in your code
  </Card>
</CardGroup>