DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to score Claude Code changes for quality during a task with Jev Review

Install Jev Review in Claude Code so the agent scores its own diff at each checkpoint.

Credentials. Your JEV_API_KEY is read by the local server and sent in the Authorization header to the Jev API, so keep it out of shared shell history and files.

Credentials. Review context you send to jev_review leaves your machine for TypeSafe's Jev API, so do not include secrets or unrelated proprietary code.

Who it is forA developer using Claude Code on a nontrivial feature who wants quality feedback before handoff.

The problemAgents finish a change without a structured check on readability, complexity, security, or test quality.

The outcomeClaude Code calls jev_review on its focused diff and reports per-dimension scores it can act on.

What you need first

  • Node.js 20 or newer
  • A Jev API key from the TypeSafe console (https://console.typesafe.ai/)
  • Claude Code, Codex, Cursor, or OpenCode installed
  • Set JEV_API_KEY with export JEV_API_KEY="your-key" before starting the coding agent

Steps

  1. Run export JEV_API_KEY="your-key" in the terminal you use to start Claude Code.
  2. Run npx plugins add NiazMorshed2007/jev-review --target claude-code.
  3. Restart Claude Code and run /mcp to confirm that jev-review is connected.
  4. Ask Claude Code to use jev-review while implementing a nontrivial change.

Prompt for your agent

Using the NiazMorshed2007/jev-review MCP tool jev_review, score my change to <target file or feature> by sending the task and focused diff. Report each applicable dimension score and confidence, then list the weakest dimensions. Verify that the tool call succeeded and that no score is missing without an applicable flag.

Caveat. Jev Review never reads your repository on its own, so the agent must send the task, diff, or files for each review.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page