> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cubic.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Developer quickstart

> Get started with cubic AI code review in minutes.

## 1. Install the cubic GitHub App

<Steps>
  <Step title="Sign up">
    Go to [cubic.dev/sign-up](https://cubic.dev/sign-up) and sign in with your GitHub account.
  </Step>

  <Step title="Install the app">
    Select the repositories you want cubic to review. You'll get 7 days free, no credit card
    required.
  </Step>
</Steps>

## 2. Trigger your first review

**Open a new pull request**

cubic automatically starts reviewing new pull requests in your selected repositories.

**Or review an existing PR**

Post this comment on GitHub to start a review:

```text theme={null}
@cubic-dev-ai review this PR
```

You'll see inline comments pointing out bugs and improvements, with explanations and
suggested fixes.

<Tip>For complex PRs, trigger an [Ultrareview](/ai-review/ultrareview) for a deeper review.</Tip>

<Tip>
  **Automatically approve clean PRs.** Enable [auto-approval](/ai-review/auto-approval) to let cubic
  approve PRs that meet your review policy.
</Tip>

## 3. Interact with cubic

### Ask follow-up questions

Reply to a review comment to ask for clarification:

```text theme={null}
@cubic-dev-ai Can you explain why this is a concern?
```

cubic responds with more context. Tell it when a finding isn't relevant to help it
[learn your team's preferences](/ai-review/memory-and-learning).

### Request a fix

Click **Fix with cubic** on a review comment, or ask cubic directly:

```text theme={null}
@cubic-dev-ai Please fix this
```

cubic generates the fix and pushes it to your PR branch. Review the changes before
merging. To get a separate PR, ask: `@cubic-dev-ai open a fix PR`.

See [Coding agents](/ai-review/coding-agents) for setup and
[Interactive comments](/ai-review/interactive-comments) for more ways to work with cubic.

## 4. Review locally with the CLI

Run a review before you push to catch issues while you're working.

Install the cubic CLI:

<Tabs>
  <Tab title="macOS and Linux">
    ```bash theme={null}
    curl -fsSL https://cubic.dev/install | bash
    ```
  </Tab>

  <Tab title="Windows">
    ```powershell theme={null}
    npx @cubic-dev-ai/cli install -g
    ```
  </Tab>
</Tabs>

Run `cubic` and sign in through your browser. Then, from your repository, review
your uncommitted changes:

```bash theme={null}
cubic review
```

To review all changes on your branch against its base, run `cubic review -b`.
Use the findings to fix issues yourself or pass them to your coding agent, then
push your changes for a GitHub review.

See [Local CLI review](/ide/cli-review) for more commands and model options.

## 5. Review the PR in cubic

Open your pull request on [cubic.dev](https://www.cubic.dev) to review the code yourself.
cubic helps you understand how the changes fit together and where to focus your attention:

* **Review related changes together.** File groups organize the diff by what changed, with explanations of the intent and behavior behind each group.
* **Get a guided walkthrough.** Ask chat to "tour this PR" for a step-by-step review of the changes and what to check.
* **Ask questions beside the code.** Select code and choose **Add to AI chat** to ask about it with the diff and codebase as context.
* **Submit your review.** Leave comments, approve, or request changes from cubic. Your review is published to GitHub.

Use the grouped diff to get oriented, then dig into the changes that need your judgment
before merging.

## Next steps

* [Connect your IDE](/ide/agent-setup) to work with review findings from your coding agent.
* [Create custom agents](/ai-review/custom-agents) for team-specific review rules.
* [Configure reviews](/ai-review/ai-review-settings) for your repositories.
* [Contact support](/account/support) if you need help.