Skip to main content
cubic can automatically fix the issues from its review. It checks each issue, pushes fixes for the real ones to your pull request, and replies on every thread. Instead of copying the Prompt for AI agents into your own coding agent, let cubic do the work. You only need to answer the questions it can’t decide alone.
Auto-fix is in alpha and available to selected teams. To try it, email contact@cubic.dev.
cubic's Confirmed reply on a resolved review thread, naming its fix commit

​
How it works

When cubic finishes reviewing your pull request, auto-fix:
  1. Checks each issue - Reads the code to see if the issue is real
  2. Fixes the real ones - Makes the change and runs your lint, type-check, and tests where it can
  3. Pushes the fix - Commits to your PR branch
  4. Replies on each thread - Explains what it decided and resolves the thread when it’s done
Each push gets a new review. Auto-fix keeps going until a review finds no open issues. This needs automatic reviews of new commits, which are on unless cubic.yaml sets reviews.incremental_commits: false. cubic's fix commit in the pull request's commit list

​
What cubic replies

Each reply starts with cubic’s decision: Want a say before it runs? Reply on the thread. If you have write access, cubic follows your reply. For example, “leave it” means cubic won’t change the code.

​
Turn on auto-fix for a pull request

The PR author and anyone with write access can turn auto-fix on or off from:
  • GitHub - Click Turn on auto-fix in the footer of cubic’s review
  • PR description - Click Turn on auto-fix next to Review in cubic
  • cubic - Use the Auto-fix switch on the PR page
  • Slack - Click Enable auto-fix on cubic’s review message
  • MCP - Ask your coding agent to call set_pr_auto_fix on the cubic MCP server
Turn on auto-fix link in the footer of cubic's review Auto-fix starts right away on any open issues. cubic pushes fixes on behalf of the person who turned it on.

​
Turn on auto-fix for a repository

Admins and members can set auto-fix in AI review → Fix with cubic, under Auto-fix:
  • Off - Auto-fix isn’t available
  • On demand (default) - Someone turns it on for each pull request
  • On - Auto-fix turns on for every pull request that matches your rules. People can still turn it off on a pull request
Auto-fix card set to On, with an Only auto-fix rule for one author and a Never auto-fix rule for bots

​
Rules

When auto-fix is On, rules pick which pull requests get auto-fix:
  • Only auto-fix when… - A pull request must match each of these. For example, an Author rule with your GitHub username runs auto-fix on your pull requests only
  • Never auto-fix when… - Any match skips the pull request. For example, skip *[bot] authors or PRs with a no-auto-fix label
Rules can match the author, label, title, head branch, or base branch. They only decide whether auto-fix starts. Once it’s on, turn it off on the pull request. You can also set the mode and rules in cubic.yaml, under issues. auto_fix_rules takes the same PR keys as auto_approve_rules: only_ or exclude_ followed by authors, labels, titles, head_branches, or base_branches.
If a rule in cubic.yaml has a blank value, a value longer than 256 characters, or an empty only_ list, cubic ignores all the rules and keeps auto-fix On demand until you fix them, or Off if the file sets auto_fix: off.

​
Follow a run

Each run opens as a fix session in Fix with cubic. You can watch the agent work and see what it fixed. You can’t send it messages. An auto-fix run's fix session in cubic, showing the agent's steps and the pushed fix Open the session from:
  • The cubic · Auto-fix check on the pull request
  • cubic’s comment on the pull request
  • The cubic PR page
Click Stop fix to stop a run, or Retry fix to rerun a failed one.

​
Stop auto-fix

  • Turn it off - From any place you can turn it on. A run in progress finishes first
  • Push your own commits - cubic stops the current run and picks up again after the next review
  • Close or merge the pull request - Auto-fix turns off

​
Tell cubic how to fix

cubic reads your repository’s AGENTS.md. Keep general guidance for coding agents there. For guidance just for cubic’s fixes, like which issues are worth fixing in your codebase, add coding agent instructions.

​
Troubleshooting

  • In AI review → Fix with cubic, make sure the Fix with cubic button is on, cubic is the coding agent provider, and auto-fix isn’t Off
  • Make sure you’re the PR author or have write access to the repository
  • Pull requests from forks aren’t supported, because cubic can’t push to them
  • Check that the repository is set to On and the pull request matches your rules
  • If someone turned auto-fix off on the pull request, it stays off there. Turn it back on from the pull request
  • With label rules, auto-fix turns on after the first review, not when the PR opens
  • After three failed runs in a row, auto-fix stops. Click Retry fix in the fix session or push a commit
  • If you pushed commits, auto-fix picks up again after cubic reviews them
  • Auto-fix doesn’t revisit an issue it already decided, but you can still ask for a fix. Comment @cubic fix this on the thread, and cubic starts a separate fix
  • For Needs your input., tag cubic with your answer, for example @cubic keep three retries and fix this