Top Repos· Jev-Based· Harness· Last updated 2026-09-21

NiazMorshed2007 / jev-review

“Local-first MCP plugin for continuous software-quality review by AI coding agents, powered by Jev.”

Jev-Based rank #19In Harness #9

• 191Stars
• —Stars Δ / 1d
• —Stars Δ / 7d
• —Stars Δ / 30d
• 17Forks
• 1Watchers

GitHub ↗Official docs ↗Back to ranking

TL;DR

NiazMorshed2007/jev-review showed up as Jev / System One related work: Agent skill, MCP, or harness that routes work through Jev-style decisions.

The author describes it as: “Local-first MCP plugin for continuous software-quality review by AI coding agents, powered by Jev.” That is their claim, not a bench this site ran.

Who it’s for

• Agent / harness authors who need a typed gate, route, or prune step
• Code-review and context-pruning workflows that must stay schema-bounded
• Anyone who needs the unofficial line: jev.pro does not issue keys and is not TypeSafe

What’s inside

Top-level entries on GitHub at generation time: .claude-plugin, .codex-plugin, .gitignore, .mcp.json, LICENSE, README.md, dist, mcp.json, package-lock.json, package.json, plugin.json, public, skills, src. Read those before you trust a one-line install.

How to use

1. Clone and follow the author’s TypeScript toolchain. Do not invent a package name.

git clone https://github.com/NiazMorshed2007/jev-review.git
cd jev-review

2. If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
3. Send a complete state and typed questions. Code owns control flow after the probabilities.

Hosted Jev still looks like a function call — wrapper or not:

{
  model: "jev-1.13.0",
  state: { source: "NiazMorshed2007/jev-review", brief: "..." },
  questions: {
    gate: { type: "noul", instructions: "Should we act on this state?" },
    route: { type: "choice", instructions: "Pick one next system.", criteria: ["code", "review", "human"] },
  },
}

Try this

Bound a review gate

Using NiazMorshed2007/jev-review, draft one Choice question: keep / summarize / drop this tool result. State must include the command, the first 2k of output, and the original user task.

Schema-safe ≠ correct

On a case NiazMorshed2007/jev-review gets wrong, write down the schema-legal answer it returned and the human label. Do not “fix” it by asking Jev to generate an explanation.

FAQ

Does this replace the TypeSafe SDK?

Only if the author implemented a full client. Most harnesses still call the vendor SDK or raw HTTP.

Are the star chips live?

Star, fork, and watcher chips refresh from the public GitHub API via a scheduled job. The prose on this page is editorial.