Skip to content
Metatext Decide — typed decisions for your agents, with a probability on every answerGet early access
Metatext
Sign Up

JevPR

GitHub App that asks Jev to classify each pull request as LOW, NORMAL or SPECIALIST risk and maps that to approve or request review.

ProjectprototypeApache-2.0
View on GitHub ↗

Overview

JevPR is a GitHub App that routes pull-request review work using Jev as the decision engine. When a pull request is opened or updated, it ingests the webhook, normalises the PR context, sends it to Jev and receives a structured risk decision such as LOW, NORMAL or SPECIALIST. A deterministic policy layer then maps that decision to an action: auto-approval, a review request to configured reviewers, or a check-run update.

The policy and reviewer list live in an optional .github/jevpr.yml file in the repository; without it a default policy applies. The service is a FastAPI app with Celery workers, PostgreSQL and Redis, and the README strongly recommends deploying with Docker Compose. It needs GitHub App permissions for checks, contents, issues, merge queues and pull requests. The author notes the project is under development and may contain bugs, and that Jev can make mistakes. It is aimed at teams wanting automated PR triage.

What the decision model decides

TypeQuestionAnswers
ChoiceWhat review level does this pull request need?LOW · NORMAL · SPECIALIST

How it works

  1. GitHub webhook fires on PR open or update
  2. Service normalises PR context and sends it to Jev
  3. Jev returns a risk class
  4. Policy in .github/jevpr.yml maps the class to approve, request review or a check-run
  5. Workers perform the GitHub actions asynchronously

Strengths

  • Per-repository YAML policy for actions and reviewers
  • Provider boundary isolates Jev
  • Docker Compose stack for deployment

Caveats

  • Under development; may contain bugs
  • Auto-approval based on a model decision carries risk
  • Requires running Postgres, Redis and a worker

Getting started

docker compose up -d --build to start the API, worker, PostgreSQL and Redis, then install it as a GitHub App.

At a glance

Type
Project
Status
prototype
Language
Python
Runtime
GitHub App (FastAPI, Celery)
Has code
yes
License
Apache-2.0

Use cases and integrations

How curated lists describe it

Frequently asked questions

What does Jev decide?

The review level of each pull request: LOW, NORMAL or SPECIALIST.

Who decides the action?

A deterministic policy configured in .github/jevpr.yml maps each level to an action.

Is it production-ready?

The README says it is under development and may contain bugs.

Related projects

  • Jevest

    Automated PR review: an LLM agent finds issues, a verifier refutes them, and Jev decides how to triage, route and label.

    ProjectproductionTypeScript
  • JevGate

    Rust code-review gate asking Jev small typed questions about functions and tests, failing CI only on rules measured 80% right.

    CLIproductionRust
  • CodeOtter★ 3

    Self-hosted PR review platform pairing an LLM narrative with a /v1/systemone decision engine for 6 rubric scores and 8 yes/no merge gates.

    Servicebeta
  • Abide

    Coding-agent hook that asks Jev one yes/no per project rule on every edit or turn and makes the agent fix any violation.

    HookbetaTypeScript
  • claude-jev

    Claude Code plugin sending small judgments to Jev: rule checks that block edits, verbatim compaction, subagent sizing and routing hints.

    PluginbetaPython
  • code-quality

    Advisor for coding agents: git and Stop hooks flag test tampering, secrets and skipped hooks, with optional Jev review findings.

    Hookbeta