jev-code-reviewer README

The project's README from github.com/egma-ai/jev-code-reviewer. As one markdown file: README.md.

Jev-Code-Reviewer

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.

Jev-Code-Reviewer on the demonstration PR

Watch the recording · Open the demo PR. The bundled recording uses real Jev classifications and labeled, prepared explanation copy (provenance).

Quick demo

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 for the replay, which makes no provider calls, or load the extension (below) and open the demo PR's Files changed page.

Review your own PR

Needs the GitHub CLI 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/<n>/files) and turn on Show logic in place of code.

Optional: 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.

Good to know

Development

npm test
node scripts/test-extension.mjs   # needs Chromium and port 4731 free

See architecture, demo guide, and extension details.

MIT.

jev-code-reviewer (egma-ai/jev-code-reviewer)

Searching Database…

144 ·GitHub
Jev-code-reviewer
What is this?Jev is a local code review tool for pull requests opened by coding agents: it classifies each diff hunk into P0, P1 or P2 attention priority and explains the change in natural language instead of raw code.
Is this a CLI tool, a browser extension, or both?It is three pieces working together: a local Node.js CLI that analyzes the diff, a Chrome extension that overlays the explanations on GitHub's Files changed page, and an agent skill your coding agent can invoke after opening a PR.
How do I review my own PR with it?Load the extension/ folder as an unpacked Chrome extension, run 'jev-reviewer token | pbcopy' and paste it into the extension's Connection popup, then open the PR's Files changed page and toggle 'Show logic in place of code'.
What do I need installed before trying it?Node.js 22+ and the GitHub CLI signed in (gh auth login), plus a local clone whose origin matches the PR's repository; an OpenAI API key is required for analysis.
Does it analyze the whole diff, and does it work on any GitHub PR page?No: only the first 12 diff hunks are analyzed by default (up to 100 with --max-units), unanalyzed files keep GitHub's original code view, and it only works on the classic Files changed page, not GitHub's new /changes page.
Does my code get sent anywhere?Yes, the analyze step sends changed code and nearby context to TypeSafe and OpenAI; the Chrome extension itself only talks to a local server on 127.0.0.1:4731.
How are the P0, P1, P2 priorities decided and can I change them?They represent how much human attention a change deserves, not correctness. P0 files open by default while P1 and P2 start collapsed, and you can retune the thresholds by copying config/policy.json into a .jev-reviewer.json file in the reviewed repo or passing --policy.
Where are my API keys stored?Keys live in ~/.config/jev-reviewer/credentials.json (owner-only, unencrypted) rather than shell exported variables, since a coding agent's shell often can't see env vars. You can swap your OpenAI key with 'node scripts/setup-keys.mjs --replace-openai'.
Can I try it without connecting my own PR?Yes, there is a bundled demo recording using real Jev classifications and prepared explanation copy that replays with no provider calls, plus an open demo PR you can load the extension against.
What happens if the PR gets new commits after I ran analyze?Old reports are never shown automatically; the extension keeps displaying GitHub's original code until you rerun analyze and click Refresh report.
What are similar projects?perch, pr-agent, no-mistakes, 1code, open-swe, open-code-review, issue-graph, diffle
Which topics is it in?pull-request, byok, devtools, code-quality, code-review, chrome-extension, browser-extension, github, cli-tool, git, local-first, coding-agent
Creator
egma-ai
Size
4 MB
Stars
144
Updated
CommitOct 05
Age
29d
Commits · 90 Days