Skip to main content
This guide walks you through setting up and using cubic’s AI code reviewer for the first time. By the end, you’ll know how to install the app, trigger reviews, interact with AI comments, and set up custom agents.

​
1. Install the cubic GitHub App

1

Sign up

Go to cubic.dev/sign-up and sign in with your GitHub account.
2

Authorize GitHub and start your free trial

Authorize cubic to access the repositories you want to review. You’ll get 14 days free, no credit card required.

​
2. Trigger your first review

To get your first AI review, you have two options: Option 1: Open a new pull request cubic automatically reviews new pull requests within a few minutes. 
git checkout -b feature/my-feature
# Make some changes
git add .
git commit -m "Add new feature"
git push origin feature/my-feature
Open the PR on GitHub, and cubic will automatically start the review. Option 2: Tag cubic in an existing PR For existing pull requests, add a comment tagging @cubic-dev-ai to trigger a review. cubic will start within a few minutes. What you’ll see:
  • A comment from @cubic-dev-ai with the PR summary
  • Inline comments on specific code changes pointing out bugs and improvements
  • Actionable suggestions with explanations

​
3. Interact with AI comments

cubic’s AI is interactive. You can chat with it, provide feedback, and request changes.
1

Ask follow-up questions

Reply to any AI comment to ask for clarification:
@cubic-dev-ai Can you explain why this is a concern?
The AI will respond with more context.
2

Provide feedback

Help cubic learn by reacting to comments:
  • Thumbs up if the suggestion is helpful
  • Thumbs down if it’s not relevant
cubic remembers your feedback and improves over time.
3

Request fixes

Ask cubic to generate a fix:
@cubic-dev-ai Can you fix this?
If background agents are enabled, cubic can automatically apply the fix.
You can also use commands like @cubic-dev-ai generate docstrings or @cubic-dev-ai explain this function directly in PR comments.

​
4. Set up your first custom agent

Custom agents enforce team-specific standards. Let’s create a simple one.
1

Navigate to custom agents

  1. Go to cubic.dev/dashboard
  2. Select your repository
  3. Click Custom Agents in the sidebar
2

Create a rule

Click New Rule and define it using natural language:Example rule:
All API endpoints must include error handling with try-catch blocks
You can also use code patterns:
Avoid using `any` type in TypeScript function parameters
3

Test the rule

Open a new PR that violates the rule. cubic will flag it:
// This will trigger the rule
function apiCall(data: any) {
  return fetch('/api', { body: data })
}
cubic will comment: “This function parameter uses any type, which violates the custom agent.”
For more advanced agent configurations, see Custom Agents.

​
5. Use background agents

Background agents automatically fix issues without manual intervention.
1

Enable background agents

In your repository settings on cubic.dev, enable Background Agents.
2

Trigger a fix

When cubic identifies an issue, you can request a fix by clicking the Fix with cubic button in the GitHub comment, or by tagging cubic:
@cubic-dev-ai Please fix this
If you want to control delivery, include “open a fix PR” or “push commits to this PR.”cubic will:
  1. Generate the fix
  2. Push commits to your PR branch or open a fix PR (depending on change size or your request)
  3. Update the comment with the result
3

Review the fix

Check the new commit to verify the changes. You can always:
  • Request modifications
  • Revert the commit if needed
  • Provide feedback for future fixes

​
6. Explore PR summaries

cubic automatically generates PR descriptions based on your code changes. When you create a PR, cubic will:
  1. Analyze the diff
  2. Generate a summary including:
    • What changed
    • Why it changed
    • Potential impacts
  3. Post it as the first comment
You can also request a summary update: 
@cubic-dev-ai update the PR summary

​
What’s next?

Now that you’ve experienced the basics, explore more features:
Have questions? Check out the FAQ section or contact support.