Set up automated code review

About

Automated code review has the Sazabi agent review pull requests on your connected forge and post inline comments plus an overall verdict. It works with both GitHub and Bitbucket.

Review runs when a pull request is opened, and — if you enable it — again when new commits are pushed to an open pull request. An explicit review request is always honored regardless of that setting.

Prerequisites

• A connected GitHub or Bitbucket integration, with the repositories mapped to the project you want reviewed.
• Project settings:write to change the review setting.

Set up in the dashboard

Automated code review is gated by a per-project master switch, then follows each integration's own setting.

Trigger a review with @Sazabi review

To request a review on demand, comment @Sazabi review on the pull request. Explicit requests run even when automatic review on new commits is off.

Agent-opened pull requests

The agent can also open a pull request with a proposed fix during an investigation. That is a separate action from reviewing an existing pull request — an agent-opened pull request lands on your forge like any other and can itself be reviewed. See Pull requests for how opening, reviewing, and asking the agent from a pull request fit together.

Set up with the CLI

Automated code review has no dedicated connect command — it is not a vendor connection but a setting on a connected forge. There is no sazabi integrations connect code-review, and the project code review master switch and each integration's review toggle are set in the dashboard under Settings > Code, not from the CLI.

The Sazabi CLI covers the prerequisite instead: connect the underlying forge from the CLI — see GitHub or Bitbucket — then enable review in Settings > Code. To request a single review on demand once review is set up, comment @Sazabi review on the pull request.

Verify

With review enabled for the project and the integration, open a small pull request on a connected repository (or comment @Sazabi review on an existing one). Confirm Sazabi posts a review with inline comments and a verdict within a few minutes. If no review appears, confirm the project master switch is on, the repository is mapped to this project, and the integration's own review setting is enabled.

Troubleshooting

No review posted — Check the project master switch under Settings > Code, that the repository is mapped to this project, and that the integration's own review toggle is on.

Review didn't re-run on a new commit — Re-review on new commits is a separate toggle. Enable it, or comment @Sazabi review to force a review.

Further reading