Get a PR reviewed with severity-ranked issues before you merge

Ask Zero to review any pull request. Zero reads the diff, flags critical issues as P0, improvement opportunities as P1, and surfaces them in Slack so the team can act before merging.

Zero verbindet:

Why PRs get merged before they should

PRs pile up. Reviewers are busy. Someone hits 'approve' to clear their queue and a subtle bug ships. Zero gives every PR a thorough read without the queue. Point it at any PR number, and it returns a structured review — critical issues that must be fixed before merge, plus lower-priority suggestions — posted directly in Slack.

How to ask Zero to review a pull request

@Zero review vm0-ai/vm0#8886

ausprobieren

How Zero reads the diff and ranks its findings

Zero reads the full diff

Zero fetches the PR via GitHub, reads every changed file, and understands the intent of the change from the PR title, description, and commit messages.

Zero ranks issues by severity

Findings are classified as P0 (must fix before merge — bugs, security issues, silent failures) or P1 (improvements — better error handling, test coverage, naming).

Review posted to Slack

Zero posts the full review in the Slack thread where it was requested, with specific file references and line numbers so the author knows exactly what to fix.

Create GitHub issues, request fixes, or verify CI status

Create a GitHub issue from a finding

Log a P0 as a tracked issue if it can't be fixed immediately

@Zero create a GitHub issue for the P0 in that review. Assign to Ethan and label as bug, priority-high.

ausprobieren

Re-review after changes

Verify that P0 feedback was addressed

@Zero re-review #8886, second commit — confirm the P0 is resolved.

ausprobieren

Check CI status

See if all checks pass before merging

@Zero what's the CI status on vm0-ai/vm0#8886? Is it safe to merge?

ausprobieren

Required integrations: GitHub

GitHub

GitHub is required. Zero needs read access to pull requests and the full diff.

Erforderlich

Slack

Slack is where the review request is made and where findings are delivered.

Optional

Best practices for AI-assisted code review

●Include the specific concern in your prompt — 'focus on auth changes' or 'check for race conditions' — to get a more targeted review than a general diff scan.

●Use re-review for iterative PRs. After the author pushes fixes, ask Zero to re-check only the P0 items to confirm they're resolved.

●Set a team norm: Zero review before any merge to main. It catches the class of issues that slip through async human review.