review-relay

Your agents judge every pull request.The lowest score counts.

Pick any coding agents or models as your panel, as many as you like. review-relay starts them the moment a review begins on GitHub, then posts one comment with their findings and a 1–5 merge confidence score.

5
4
5

acme/billing #482

Retry failed invoice webhooks

4/5

Merge confidence

Lowest of 3 judges on 9f3c2a1

Example panel on a fictional repo with three configured agents.
$ curl -fsSL https://downloads.reviewrelay.dev/install.sh | bash

Installs a standalone binary and verifies its checksum. Run it again to update.

The scoresheet

Every judge scores the same six dimensions from 1 to 5. Findings cap the score, so the number never outruns the problems. The comment’s headline is the lowest judge.

Set the severity of the retry-loop finding

Headline score 4

A minor finding leaves the score alone.

Retry failed invoice webhooks

acme/billing #482 · 9f3c2a1

Example review on a fictional repo with three configured agents.

DimensionAgent AAgent BAgent C
Correctness545
Security555
Code quality445
Standards544
Blast radius444
Testing534
Merge confidence545

Findings (2)

  • minorsrc/invoices/retry.ts:57Retry loop has no cap on total delay (Agent A, Agent B)
  • minorsrc/invoices/retry.test.tsNo test for the exhausted-retries path (Agent B)

Order of events

Nothing to click. The panel convenes on its own, and GitHub events reach your machine through gh webhook forward, so there is no public URL to host.

  1. A review starts

    Greptile’s check run begins, a pull request is opened or marked ready, or a collaborator comments @review-relay. Each repo picks its trigger: auto, greptile, or github.

  2. The commit is checked out locally

    review-relay fetches the PR head into a temporary worktree of your own clone, so the panel reads real code using your own agent logins and keys.

  3. The panel reviews in parallel

    Every agent you configured, on whichever harness or model, reviews read-only against the same rubric: your repo's conventions, lint config, and the callers of changed code.

  4. One scored comment lands

    Findings are merged across judges and linked to exact lines. Later reviews edit the same comment. Each commit is reviewed once, and drafts wait until they are ready.

Before the panel sits

review-relay drives tools you already use. Have these signed in first.

  • gh signed in with access to the repos you watch, plus its webhook extension:
    $ gh extension install cli/gh-webhook
  • The coding agents or models you want judging, signed in or set up with an API key
  • A local clone of each repo you want reviewed

The installer writes an example config to ~/.review-relay/config.json. Point it at your repos and local clones, list the agents on your panel, then start watching:

$ review-relay start$ review-relay status

Reviews run from your machine, and your code goes to whichever providers your chosen agents and models use.

Seat your panel.

Free to use. One command installs a standalone binary for macOS, Linux, or Windows.

$ curl -fsSL https://downloads.reviewrelay.dev/install.sh | bash