Skip to content
Back to search

jev-code-reviewer

Review behavior, not just diffs. Jev prioritizes human attention; OpenAI explains the changes. Local CLI + agent skill + GitHub extension.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/egma-ai--jev-code-reviewer/badge.svg)](/listings/egma-ai--jev-code-reviewer)

HTML

<a href="/listings/egma-ai--jev-code-reviewer"><img src="/api/listings/egma-ai--jev-code-reviewer/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 62 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Jev-Code-Reviewer
  2. Most PRs that are getting generated by agent hard for human mind to comprehend as it shows up with lot of file changes at once. 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.
  3. It runs on your computer, for reviewing your own coding agent's PRs, and posts nothing to GitHub.
  4. ![Jev-Code-Reviewer on the demonstration PR](docs/preview.png)
  5. [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](demo/README.md)).
  6. ## Quick demo
  7. Needs Node.js 22+.
  8. ```sh
  9. git clone https://github.com/egma-ai/jev-code-reviewer.git
  10. cd jev-code-reviewer
  11. npm install
  12. npm run demo
  13. ```
  14. 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](https://github.com/egma-ai/jev-code-reviewer/pull/1/files).
  15. ## Review your own PR
  16. Needs the [GitHub CLI](https://cli.github.com/) signed in (`gh auth login`) and a local clone whose `origin` is the PR's repository.
  17. ```sh
  18. npm link # adds the jev-reviewer command
  19. jev-reviewer setup # stores your TypeSafe and OpenAI keys; run it in your own terminal
  20. jev-reviewer doctor # checks tools, key sources, the local server, and provider access
  21. jev-reviewer serve # leave running
  22. jev-reviewer analyze --pr https://github.com/OWNER/REPO/pull/123 --repo /path/to/clone
  23. ```
  24. Then in Chrome:
  25. 1. Open `chrome://extensions`, turn on **Developer mode**, click **Load unpacked**, and pick this repo's `extension/` folder.
  26. 2. Run `jev-reviewer token | pbcopy`. In the extension popup, open **Connection**, paste, and click **Save**. It should say **Paired**.
  27. 3. Open the PR's **Files changed** page (`/pull/<n>/files`) and turn on **Show logic in place of code**.
  28. 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](install/README.md).
  29. ## Good to know
  30. - **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`.
  31. - **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`.
  32. - **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.
  33. - **Classic Files changed page only.** GitHub's new `/changes` page is not supported yet; switch back under your profile picture → **Feature preview**.
  34. - **Old reports are never shown.** If the PR has newer commits, the extension keeps GitHub's code: rerun `analyze`, then click **Refresh report**.
  35. - **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`.
  36. ## Development
  37. ```sh
  38. npm test
  39. node scripts/test-extension.mjs # needs Chromium and port 4731 free
  40. ```
  41. See [architecture](docs/ARCHITECTURE.md), [demo guide](docs/DEMO.md), and [extension details](extension/README.md).
  42. MIT.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.