Releash
Start with GitHub

Human-in-the-loop review

Review the critical 5%, skip the rest.

Releash holds the leash on every pull request your agents open, flags only the code paths a human must see, and blocks the merge until each one is approved.

Start with GitHubSee how it works

Works with GitHub and GitLab · The check fails until every critical path is approved

A run, end to end

One flagged range, the reasoning behind it, and the check that holds the merge. Nothing else from the diff makes it here.

acme/payments #482

Finalize the review gate

2 pending
49const findings = await loadFindings(db, runId);
50+if (findings.some((f) => f.status !== 'approved')) return;
51+await markRunComplete(db, runId);
52+await approve();
53}

A run could be marked complete while a critical path was still pending.

auth · high

1 of 3 critical paths approved

releash/review failing

The loop

Four steps, none of them yours to configure

Releash is a GitHub App and a small review surface. It does not replace your reviewers; it tells them where to look.

  1. 01

    Watch every pull request

    Opened, reopened, or pushed to. No branch allow-lists to maintain. Drafts wait until they are marked ready.

  2. 02

    Flag the critical ranges only

    Auth, payments, migrations, secrets, concurrency, public contracts. Not formatting, tests, or lockfiles.

  3. 03

    Approve or comment in place

    You see the flagged lines, not four thousand of them. Comments post back into the GitHub review.

  4. 04

    Unblock the merge

    The required check stays failing while anything is unapproved. The final approval turns it green.

The rubric

What it considers critical

The reviewer agent runs one fixed rubric so every pull request is judged the same way. It flags ranges, never prose, and never writes your review for you.

Concurrency and idempotency, public API contracts, and anything your team marks as sensitive are covered too. You can add your own paths.

  • authsessions, permission checks, login and token flows
  • paymentsbilling, pricing, refunds, anything moving money
  • datadestructive queries, deletions, schema changes
  • securitysecrets, crypto, redaction, input trust
  • migrationschema and backfill migrations
  • infradeploy config, CI credentials, infrastructure as code

The rest of the diff can wait.

Install the app, open a pull request, and watch what it refuses to let through.

Start with GitHubPricing