Skip to content
System One

Jev for coding agents and code review: 83 projects

A coding agent reads a repository, edits files and runs tools, and it asks itself small questions all session long. Which file matters here? Is this command safe? Did that test fail for a real reason? A decision model answers those questions with a typed choice or score and a confidence value, so the harness can act on the result in code instead of parsing a paragraph. The examples in this hub run on Jev and other decision models. Some label pull requests, such as 1jehuang/jev-pr-labeler, or pick which tests a change can skip, such as baronunread/leanest. Others sit inside an agent as a gate or a router, like clownware/bouncer, a Claude Code hook that scores each tool call against a policy file. Many ship as plugins or skills for Claude Code, Codex or Pi. Before you copy one, check which agent it targets, what the decision model is shown, what happens when confidence is low, and whether it fails open to the normal path or blocks the agent.

83 entries

All entries

Showing 1 to 48 of 83

How decision models are used for coding agents

In practice the decision model handles the narrow, repeated questions and the coding LLM keeps the writing. devagrawal09/stanley-code is a command-line toolkit an agent can delegate to for ranking relevant files, checking a diff against its task and project rules, and triaging test failures. cephalization/jev-triage asks a fixed set of typed questions per GitHub issue, such as what kind it is and how severe.

Score fits ranking jobs like picking relevant files or tests. Choice fits labelling and routing. Noul, a yes or no with a probability, fits gates such as whether a tool call is destructive. A hook like clownware/bouncer turns the answer into allow or deny with plain code, so a person owns the policy file. The answer is a number or a label, so the hook or plugin can compare it with a threshold in code.

The trade-off is where the check sits. A gate on every tool call adds a decision to every step. Entries such as baronunread/leanest fail open to the full test suite when the model is unsure, so a wrong call costs time instead of a missed bug. Pick the failure mode before you pick the tool. Read each entry's docs for which way it fails.

FAQ

Can Jev review code or pull requests?

Entries here use Jev to label pull requests by the size of the change, classify commits, triage issues and check a diff against project rules. It returns typed answers with confidence, so a CI step or agent can act on them. It does not write the review text.

How do I use Jev with Claude Code or Codex?

Most entries ship as a hook, plugin or skill. A hook runs before or after a tool call and asks Jev a question about it. Read each project's install notes, since they target different agents and versions.

Does a decision model replace the coding LLM?

No. The coding LLM still writes and edits code. The decision model answers small questions around it, such as which file is relevant or whether a command is safe.