Skip to main content
SlothBot checks the changes in a review for bugs and leaves comments on the code. It can read related files in the repository to understand how the changes fit together. Human reviewers can keep reviewing while SlothBot works.
AI reviews are available on Studio and Enterprise plans, and during an active trial or grace period. Your organization must have SlothBot enabled.

​
Request a review in the app

  1. Create a review between two branches, or open an existing one.
  2. Add a title and description that explain the intent of the changes. SlothBot uses them as context.
  3. Click Review with SlothBot on the review page.
Review with SlothBot button below the Reviewers list
  1. Wait for the queued and reviewing states to finish. You can leave the page; SlothBot runs on the server.
  2. Read the findings in Conversation and Files changed. The status shows the reviewed commit, files reviewed, findings, and files skipped.
Completed SlothBot review showing the reviewed commit and counts of reviewed files, findings, and skipped files You need write access to the repository and read access to all its files. The review must be open and compare two branches. When SlothBot finds no issues in the files it reviewed, it leaves a short summary comment. A review with only skipped files can finish without a comment. SlothBot does not approve, merge, or change your code. Check its findings before acting on them; it can miss bugs or report something that is not a bug. To find reviews that SlothBot has checked, choose SlothBot in the Reviews list’s Reviewer filter. Use the thumbs-up or thumbs-down reaction on a SlothBot comment to share whether it was helpful. Click the same reaction again to remove it.

​
Request a review from the CLI

From your feature branch, create a review and request SlothBot:
To request both SlothBot and a teammate, use a comma-separated list:
Request SlothBot on an existing review:
Check the status:
The request returns while SlothBot works. Open the printed review link to read its comments. If the AI request fails after the review was created, the review still exists; use review edit to retry. See the review command reference for other options.

​
Review new changes

After committing more changes to the review branch, request SlothBot again. Reviews do not rerun automatically. Each result identifies the commit it checked. A completed result is reused when the compared changes are unchanged. Editing only the review title or description does not start a new AI review. Earlier comments remain in the conversation after new commits; their inline locations may no longer appear.

​
Limits and failures

  • Text files: binary files, including images, models, and Unreal assets, are skipped. Files larger than 512 KB on either side are also skipped.
  • Large changes: file and input-size limits can leave some files unreviewed. Check the skipped-file count and use smaller reviews when possible.
  • Repository context: SlothBot can read related files, but does not run the code or tests and does not search the contents of the entire repository.
  • Usage: AI reviews share your organization’s AI token budget. If it is exhausted, wait and try again later.
  • Failed runs: the review page shows an error. Retry with Review with SlothBot after addressing it. If the branch changed while SlothBot was working, request a review of the latest changes.
If the button is missing, check with your organization admin that SlothBot and AI reviews are available for your organization. A plan upgrade does not override an organization setting that disables SlothBot.

​
Your data

SlothBot runs when someone requests a review. Diversion sends the changed code, selected repository context, review title and description, and earlier review comments to a third-party AI provider. You do not need your own API key to use AI reviews in Diversion’s cloud service.