{"slug": "jev-based-code-review", "title": "Jev Based Code Review", "summary": "Egma AI released Jev Code Reviewer, an MIT-licensed local tool that classifies each change in an agent-generated pull request as P0, P1 or P2 and shows only P0 diffs by default, with diffs rendered in natural language and the original code one toggle away. The tool runs on the reviewer's own machine, requires Node.js 22+ and the signed-in GitHub CLI, and posts nothing to GitHub; it sends changed code and nearby context to TypeSafe and OpenAI, caps analysis at the first 12 diff hunks in path order (up to 100 via --max-units), and only works on GitHub's classic Files changed page.", "body_md": "Most PRs that are generated by agents today get YOLO merged because its hard for human mind to comprehend when your agent just suddenly shows up with 230 file changes. This is an attempt to reduce the mental burden by classifying each change in a review to P0, P1, P2. Only P0 are shown by default. The priorities are configurable. The diffs are also show using a natural language. The original code is one toggle away.\n\nIt runs on your computer, for reviewing your own coding agent's PRs, and posts nothing to GitHub.\n\n[Watch the recording](https://github.com/egma-ai/jev-code-reviewer/blob/main/docs/demo.mp4) · [Open the demo PR](https://github.com/egma-ai/jev-code-reviewer/pull/1). The bundled recording uses real Jev classifications and labeled, prepared explanation copy ([provenance](https://github.com/egma-ai/jev-code-reviewer/blob/main/demo/README.md)).\n\nNeeds Node.js 22+.\n\n```\ngit clone https://github.com/egma-ai/jev-code-reviewer.git\ncd jev-code-reviewer\nnpm install\nnpm run demo\n```\n\nOpen [http://127.0.0.1:4731/demo](http://127.0.0.1:4731/demo) for the replay, which makes no provider calls, or load the extension (below) and open the [demo PR's Files changed page](https://github.com/egma-ai/jev-code-reviewer/pull/1/files).\n\nNeeds the [GitHub CLI](https://cli.github.com/) signed in (`gh auth login`) and a local clone whose `origin` is the PR's repository.\n\n```\nnpm link                 # adds the jev-reviewer command\njev-reviewer setup       # stores your TypeSafe and OpenAI keys; run it in your own terminal\njev-reviewer doctor      # checks tools, key sources, the local server, and provider access\njev-reviewer serve       # leave running\njev-reviewer analyze --pr https://github.com/OWNER/REPO/pull/123 --repo /path/to/clone\n```\n\nThen in Chrome:\n\n1. Open `chrome://extensions` , turn on**Developer mode** , click**Load unpacked** , and pick this repo's`extension/` folder.\n2. Run `jev-reviewer token | pbcopy` . In the extension popup, open**Connection** , paste, and click**Save** . It should say**Paired** .\n3. Open the PR's **Files changed** page (`/pull/<n>/files` ) and turn on**Show logic in place of code** .\n\nOptional: `uv tool install graphifyy` adds a local code graph for better context. To have your coding agent run `analyze` after it opens a PR, install the [agent skill](https://github.com/egma-ai/jev-code-reviewer/blob/main/install/README.md).\n\n- **Your code leaves your machine.**`analyze` sends changed code and nearby context to TypeSafe and OpenAI. The extension only talks to the local server on`127.0.0.1:4731` .\n- **Keys** are stored in`~/.config/jev-reviewer/credentials.json` (owner-only, not encrypted). Prefer this over exported variables, which a coding agent's shell often cannot see. Replace an OpenAI key with`node scripts/setup-keys.mjs --replace-openai` .\n- **Coverage is capped.** The first 12 change units (diff hunks) in path order are analyzed;`--max-units` allows up to 100. Files with an unanalyzed change keep GitHub's code, and the CLI and popup say how many.\n- **Classic Files changed page only.** GitHub's new`/changes` page is not supported yet; switch back under your profile picture →**Feature preview** .\n- **Old reports are never shown.** If the PR has newer commits, the extension keeps GitHub's code: rerun`analyze` , then click**Refresh report** .\n- **Priorities mean attention, not correctness.** P0 files open by default; P1 and P2 start collapsed. Tune them by copying`config/policy.json` to`.jev-reviewer.json` in the reviewed repo, or pass`--policy` .\n\n```\nnpm test\nnode scripts/test-extension.mjs   # needs Chromium and port 4731 free\n```\n\nSee [architecture](https://github.com/egma-ai/jev-code-reviewer/blob/main/docs/ARCHITECTURE.md), [demo guide](https://github.com/egma-ai/jev-code-reviewer/blob/main/docs/DEMO.md), and [extension details](https://github.com/egma-ai/jev-code-reviewer/blob/main/extension/README.md).\n\nMIT.", "url": "https://wpnews.pro/news/jev-based-code-review", "canonical_source": "https://github.com/egma-ai/jev-code-reviewer", "published_at": "2026-09-25 04:49:23+00:00", "updated_at": "2026-09-25 04:59:53.867212+00:00", "lang": "en", "topics": ["ai-agents", "developer-tools", "ai-tools", "ai-products"], "entities": ["Egma AI", "Jev Code Reviewer", "GitHub", "TypeSafe", "OpenAI", "Node.js", "GitHub CLI", "Chrome"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/jev-based-code-review", "markdown": "https://wpnews.pro/news/jev-based-code-review.md", "text": "https://wpnews.pro/news/jev-based-code-review.txt", "jsonld": "https://wpnews.pro/news/jev-based-code-review.jsonld"}}