jev-reviewer

jev-reviewer command [options]

jev-reviewer is the command installed by the Jev-Code-Reviewer project (`npm` package name `jev-reviewer`, binary `bin/jev-reviewer.mjs`). It is a local review aid for pull requests that are too large to read as a raw diff. TypeSafe's Jev model assigns each analyzed change an attention priority. OpenAI writes the prose a reviewer sees instead of the diff: old logic, new logic, what changed, and why a person might need to look. Priorities mean attention, not correctness.The bundled policy (`config/policy.json`) uses three levels. P0 is human judgment required (permissions, security boundaries, destructive operations, incompatible contracts, or a consequential decision). P1 is human review recommended. P2 is low attention (documentation, formatting, mechanical edits, or a refactor that looks behavior-preserving). Uncertain changes default to P0 (`uncertainPriority` may be P0 or P1, never P2). The extension shows P0 files expanded and starts P1 and P2 collapsed. A repository may replace the policy with `.jev-reviewer.json`, or --policy can point at another JSON file. A path matching `alwaysReviewPaths` is forced to P0. The bundled patterns are `/auth/`, `/migrations/`, and `/.github/workflows/`. Incomplete or unsupported diffs are also kept at P0 or raised to `uncertainPriority`.The Chrome extension is loaded unpacked from the repository's `extension/` directory. It only changes GitHub's classic Files changed page (`/pull/<n>/files`). The newer `/changes` page is not supported. When the server is down, the report is missing, or the report is older than the pull request's latest commit, the extension leaves GitHub's diff in place. Pair it with `jev-reviewer token`.The package is `"private": true` and is not published to npm. Install from a checkout with Node.js 22 or newer: `npm install`, then `npm link` so `jev-reviewer` is on `PATH`. `git` and the GitHub CLI (`gh auth login`) are required for `analyze`.

setup

Prompt in the terminal for `TYPESAFEAPIKEY` and `OPENAIAPIKEY` and store them. Input is hidden. Requires an interactive terminal; do not pass key values as arguments. A key already in the credentials file is left as-is. A key present only in the environment can be copied into the file. To replace a stored OpenAI key, run `node scripts/setup-keys.mjs --replace-openai` from a checkout.

Check required tools, where each key comes from, the local server, and provider access. --offline skips the live provider requests. --port is the server port to probe (default 4731). Exits non-zero when a check fails.

Classify committed changes on a GitHub pull request. --pr is the pull-request URL. --repo is the local clone whose `origin` is that repository (default: the current directory). Needs `git` and an authenticated `gh`. Resolves the base and head commits, splits the diff into change units (hunks), and analyzes the first --max-units of them in path order (default 12, range 1–100). The rest stay as GitHub's original diff and are marked not analyzed. Before analysis it makes one small request to each provider and stops if either fails. Writes a report under `~/.cache/jev-reviewer/reviews`. --output also writes that report to file; the copy contains source excerpts. Does not post anything to GitHub.

Serve cached reports on `127.0.0.1` (default port 4731) for the unpacked Chrome extension. Ctrl-C stops it.

Start the same local server and point at the bundled recorded demo. Makes no TypeSafe or OpenAI calls. The recorded explanations are prepared demonstration copy, not a live model run.

Print the local pairing token the extension stores under Connection. This is not a model-provider key. Treat it as local access material.

Print the command summary. Also printed when no command is given.

analyze only. Try Graphify for related symbols and dependencies, or skip it. Graphify is on by default and the run falls back to the diff and nearby source when it is unavailable. Install with `uv tool install graphifyy` when you want the graph.

~/.config/jev-reviewer/credentials.json

`TYPESAFEAPIKEY` and `OPENAIAPIKEY`. Created by setup with owner-only permissions (directory `0700`, file `0600`). Not encrypted. A stored key wins over the same variable in the environment.

Accepted from the environment when the credentials file has no value for that key. Shells that do not export them, including many coding-agent shells, will not see them. Prefer the credentials file.

Optional policy in the repository being reviewed. Overrides the bundled `config/policy.json`. --policy overrides both. The policy hash is stored in the report. Policy is operator configuration: it is read from the working tree separately from the commits under review.

Cached reports. The file for a pull request is `{owner}--{repo}--{number}.json`. `serve` reads this directory and answers only on loopback. The extension requests `GET /api/reviews/{owner}/{repo}/{pullRequest}` with the pairing token. JEV_REVIEWER_CACHE_DIR replaces the `~/.cache/jev-reviewer` root.

Created on the first token run (32 random bytes, hex, mode `0600`). JEV_REVIEWER_CONFIG_DIR replaces the `~/.config/jev-reviewer` directory for this file. The credentials file above stays at its own path.

Live `analyze` sends changed code and nearby context to TypeSafe and OpenAI. The extension itself talks only to `127.0.0.1`. There is no hosted Jev-Reviewer backend and nothing is posted back to GitHub.Only the first 12 change units are analyzed unless --max-units is raised (maximum 100). Units past the cap keep GitHub's diff.`demo` does not exercise the live providers. Its classifications are a recorded Jev run; its explanations are prepared copy.The project describes itself as a local prototype (version 0.1.0). Reports go stale when the pull request gains commits; rerun `analyze` and refresh the extension.

jev-reviewer was published by the egma-ai organization in September 2026 (GitHub repository created on 19 September 2026, version 0.1.0). It is MIT-licensed. The command is the local half of a three-part tool: this CLI, an agent skill that can run `analyze` after opening a pull request, and a Chrome extension that overlays the report on GitHub.

jevchat(1), jevals(1), gh(1), git(1), node(1), npm(1)

Source code · Documentation