PR Judge — should this pull request merge?
Paste a public GitHub PR. Jev reads the diff and returns a verdict — SAFE TO MERGE, NEEDS REVIEW or BLOCK — with structured checks, in one API call. No key, just paste.
Any public GitHub pull request. We read its diff + metadata and Jev returns a verdict in one call.
How PR Judge works
Paste any public GitHub pull request URL. We fetch its diff and metadata (title, files changed, additions and deletions) and send them to the Jev decision API as a single typed request: a choice between SAFE TO MERGE, NEEDS REVIEW and BLOCK, plus a set of yes/no and score checks. Jev returns a verdict with a calibrated confidence in roughly a second — one call, structured output you can act on.
This is exactly the shape of decision Jev is built for: read a situation, return a typed judgment. Here it triages a PR; in a real pipeline you would call the same API to gate merges, route reviews, or flag risky changes automatically.
What the checks mean
- Verdict — SAFE TO MERGE / NEEDS REVIEW / BLOCK, the headline call.
- Risk — a none→critical score for merging the change.
- Touches security / auth / infra — flags changes to sensitive paths.
- Adds or updates tests — whether the PR ships tests for its changes.
- May break existing behavior — a heads-up on contract/behavior risk.
- Easy to revert & size — how reversible and how large the change is.
Build it into your own pipeline
PR Judge is a thin wrapper over the Jev API. With a hosted key you can run the same decision from a GitHub Action or bot: post the verdict as a check, auto-approve low-risk PRs, or require review on anything that touches critical paths — a typed choice/score/noul call in about 100–300ms, for a fraction of a cent.
FAQ
Does this replace human code review?
No. PR Judge is a one-call triage demo — it helps you spot risky or review-worthy PRs fast, but it does not read your whole codebase or run your tests. Treat it as a first-pass signal, not an approval.
Does it work on private repositories?
No — it only reads public GitHub pull requests. For private repos you would run the same Jev call from inside your own CI, where you already have access to the diff.
Is it free? Do I need a key?
It is free and needs no API key — each judgment is a rate-limited call to the live Jev decision API. To run it in your own pipeline, get a hosted jv_live_ key on the pricing page.
How fast and cheap is a verdict?
One API call, usually about a second end to end (including fetching the diff from GitHub), costing a fraction of a cent in input tokens. The result shows the latency and cost.
More: All Jev tools · Agent Risk Checker · Jev API docs · Watch Jev play 2048