Skip to main content
cubic can automatically fix issues identified during code review. Request a targeted fix with one click. Fix with cubic button

​
How it works

When cubic identifies an issue in your code, you can request an AI-generated fix that:
  1. Analyzes the issue - Reviews the problem and relevant context
  2. Generates a solution - Creates a targeted fix addressing the specific issue
  3. Applies the fix - Pushes commits to your PR branch by default, or opens a fix PR when requested
  4. Preserves review flow - Lets you review the changes before merging into your main PR
By default, cubic pushes commits directly to your PR branch. To override, include “open a fix PR” in your request. If cubic opens a fix PR, it targets the branch of your original PR, not the main branch.

​
Triggering fixes

There are two ways to request an AI fix:

​
Tagging cubic in Github or cubic

Request AI fix demo You can also request fixes for issues cubic didn’t flag. Tag cubic in any PR comment (including colleague comments) and ask for a fix:
  • “@cubic fix this issue”
  • “@cubic-dev-ai can you generate a fix for this?”
  • “@cubic please fix the type error mentioned above”
cubic will acknowledge your request and begin generating the fix. If you want a separate PR instead of direct commits, say “open a fix PR.”
cubic only treats the current comment as permission to edit code when that comment explicitly tags cubic. @cubic, @cubic-dev-ai, and other supported cubic tags work. Replying inside a cubic-started thread without a fresh tag is treated as discussion, feedback, or questions, not authorization to push changes.

​
Using the fix button in cubic

Fix button For inline review comments, click the Generate fix button in the comment actions menu. Dashboard-triggered fixes commit directly to the PR’s branch by default. This is available when:
  • The comment identifies a specific issue in a file
  • The comment includes file and line context
  • Your installation has the fix feature enabled

​
What to expect

​
Fix generation process

  1. Acknowledgment - cubic reacts with 👀 and comments
  2. Analysis - The AI analyzes the issue and surrounding code
  3. Delivery - cubic pushes commits to your PR branch by default, or opens a fix PR if requested. Claude Code runs in an ephemeral container in the background. (typically 1-3 minutes)
  4. Notification - cubic updates the original comment with the commit or PR details

​
Reviewing changes

If cubic opens a fix PR, it includes:
  • Descriptive title - AI-generated title explaining what’s being fixed
  • Targeted changes - Only the code needed to address the specific issue
  • Original context - Reference to the original PR and issue comment
  • Clean diff - Easy to review changes in isolation
If a fix PR is created, you can test the changes locally by checking out the fix branch before merging.
If cubic pushes commits directly, review the new commits on your PR branch as usual.

​
Best practices

​
Tips for using AI fixes

  • Review carefully - Always review AI-generated code before merging
  • Test locally - Verify the fix works as expected in your environment

​
Limitations

  • Complex architectural changes may require manual intervention
  • Fixes are scoped to the specific issue identified
  • Some issues may require broader refactoring beyond a single fix
  • Follow-up changes are not yet supported
  • Generated PRs or pushed commits run through your existing GitHub CI checks

​
Integration with your workflow

Fixes integrate seamlessly with your existing review process:
  1. Review the change (fix PR or new commits on your PR branch)
  2. Merge when satisfied if a fix PR was opened
  3. Continue with your original PR now including the fix
  4. Single deployment - Everything ships together
This keeps git history clean while enabling granular review.