How it works

How Reviewz turns PR volume into safe human review actions.

Reviewz sits before GitHub review. It observes GitHub facts, builds advisory review briefs, and routes humans to the next safe verification step.

Request beta accessBack to home

Workflow

Reviewz fits around your GitHub review flow.

Connect selected repositories

Install the Reviewz GitHub App, authorize selected repositories, then enable Reviewz only where you want guidance.

Observe GitHub facts

Reviewz reads observable pull request signals: PR state, draft status, head SHA, changed files, checks, branch context, stack context, and available repository policy signals.

Build one safe action

Each PR gets one primary action: inspect draft, open review brief, verify in GitHub, follow specialist guidance, or use historical context only.

Start with context

Reviewz shows why the PR matters, how deeply to review, where to start, and what evidence is not visible.

Decide in GitHub

Humans still read the diff, comment, mark files viewed, approve, request changes, or merge in GitHub.

Safe action anatomy

What a safe review action contains.

Advisory · Not a merge decision. Illustrative example, not customer data. Final review stays in GitHub.

PR #1842 — Deep review recommended

Decision to make
Can this session-policy change be reviewed confidently without revoked-session regression coverage?
Start here
src/auth/session_policy.ts — this file carries the review decision.
Then verify
tests/auth/session_policy.test.ts — verify revoked-session coverage.
GitHub confirms
PR is open.Head SHA observed.CI status observed.Required checks remain final in GitHub.
Reviewz infers
Auth/session behavior changed.Sensitive path touched.Regression evidence appears limited.
Not visible to Reviewz
No visible regression test covers expired refresh token + revoked session.
Next safe action
Open GitHub PR, review the session policy change first, then verify or request missing regression coverage.

Recommended action

Inspect draft, open review brief, verify in GitHub, follow specialist guidance, or use historical context only.

Why now

Sensitive paths, large diffs, dependency impact, update signals, and evidence gaps explain why the PR deserves attention.

Review depth

Quick, standard, deep, specialist, draft inspection, or GitHub verification.

Start here

A file or area that carries the review decision, not just the largest diff.

GitHub confirms

Open state, head SHA, changed files, checks observed, and other facts visible to Reviewz.

Not visible to Reviewz

Evidence gaps are named as not visible instead of being overstated.

Lifecycle states

Same state, same meaning, safe action.

Current guidance

Use the active Reviewz brief as reviewer context, then finish the decision in GitHub.

Draft

Drafts are inspect-only. Formal review waits until the PR is ready for review.

Stale

If the head changes, previous guidance is orientation only and the reviewer goes back to GitHub.

Verify in GitHub

Reviewz points back to GitHub when GitHub needs to confirm the current state.

Outside guidance

A PR without Reviewz guidance remains visible with a reason and a safe action.

Historical

Closed or merged PRs can provide context, but they are not active review tasks.

Evidence model

Evidence is separated from inference.

GitHub facts

Facts observed from GitHub stay separate from Reviewz interpretation.

Reviewz inference

Risk, depth, and start-target guidance are advisory signals for the reviewer.

Not visible

Reviewz says what it cannot see instead of claiming a fact it cannot prove.

AI enrichment

When AI enrichment is enabled, PR diff context is sent to Anthropic.

Fallback

If enrichment is unavailable, Reviewz falls back to deterministic guidance and surfaces that state.

Command Palette

Jump from a PR number, repository, or start file to the next safe review action.

Trust

GitHub remains final.

Files and diff

GitHub remains the final surface for reading changed files and marking files viewed.

Reviews

Comments, approvals, request changes, and merge decisions stay in GitHub.

Required checks

Reviewz may observe check status, but required checks must be verified in GitHub before final decision.

Advisory Check Runs

Reviewz Check Runs are advisory review guidance, not approval or merge readiness.

Repository control

GitHub authorization and Reviewz enablement are separate. Reviewz only runs on repositories you enable.

No merge authority

No personal access tokens required. No code or branch changes. No merge authority.

FAQ

Detailed workflow FAQ

The longer answers behind the shorter home page.

Is Reviewz an AI code reviewer?

No. Reviewz is a review decision layer for humans.

It may use AI to enrich review guidance, but its job is not to approve code or replace reviewers.

Its job is to tell reviewers what human verification is needed next, where to start, and what evidence still needs to be checked in GitHub.

Does Reviewz replace human code review?

No.

Reviewz prepares the review path.

Humans still read the diff, comment, approve, request changes, and merge in GitHub.

Can Reviewz approve or block a pull request?

No.

Reviewz does not approve, request changes, block merges, or claim merge readiness.

Reviewz guidance is advisory.

What happens when Reviewz is unsure?

Reviewz makes uncertainty visible.

A PR may be marked as needing GitHub verification, stale guidance, outside guidance, deterministic fallback, or historical context.

What if a PR is a draft?

Draft PRs are inspect-only.

Reviewz can help reviewers understand risk or context, but it does not present drafts as ready for formal review.

Does installing the GitHub App make our code public?

No.

Installing the GitHub App grants Reviewz access only to the repositories you select. It does not make your repositories public, and it does not expose Reviewz source code.

Does Reviewz send code to an LLM?

Reviewz can use AI enrichment to improve review guidance when enabled.

When AI enrichment is enabled, PR diff context is sent to Anthropic.

GitHub facts and deterministic safeguards remain the base layer.

If enrichment is unavailable, Reviewz falls back to deterministic guidance and surfaces that state.

Can we start with selected repositories only?

Yes.

GitHub authorization and Reviewz enablement are separate.

You choose which repositories GitHub authorizes, then choose which repositories Reviewz enables.

Reviewz only runs on repositories you enable.

What if a PR has no Reviewz guidance?

Reviewz shows that state instead of hiding it.

The PR can appear as no active Reviewz guidance, stale, historical, or needing GitHub verification, with a safe action back to GitHub.

Why not just use GitHub?

GitHub remains the source of truth and the final review surface.

Reviewz sits before GitHub to help reviewers decide what needs attention first, how deeply to review, where to start, and what evidence to verify.

What does Advisory mean?

Advisory means Reviewz provides review guidance, not approval or merge readiness.

Reviewz Check Runs are advisory review guidance.

GitHub remains the source of truth for checks, reviews, approvals, request changes, and merge.

Request beta access