Jev Based Code Review 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. 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. It runs on your computer, for reviewing your own coding agent's PRs, and posts nothing to GitHub. 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 . Needs Node.js 22+. git clone https://github.com/egma-ai/jev-code-reviewer.git cd jev-code-reviewer npm install npm run demo Open 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 . Needs the GitHub CLI https://cli.github.com/ signed in gh auth login and a local clone whose origin is the PR's repository. npm link adds the jev-reviewer command jev-reviewer setup stores your TypeSafe and OpenAI keys; run it in your own terminal jev-reviewer doctor checks tools, key sources, the local server, and provider access jev-reviewer serve leave running jev-reviewer analyze --pr https://github.com/OWNER/REPO/pull/123 --repo /path/to/clone Then in Chrome: 1. Open chrome://extensions , turn on Developer mode , click Load unpacked , and pick this repo's extension/ folder. 2. Run jev-reviewer token | pbcopy . In the extension popup, open Connection , paste, and click Save . It should say Paired . 3. Open the PR's Files changed page /pull/