User repository on GitHub
- Forks
- 4
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.
CommunityJev Agents & MCP
Oxlint Plugin Jev
Experimental oxlint plugin that turns plain-English yes/no questions into lint rules, answered by TypeSafe Jev with a probability you threshold.
- Stars
- 86
- Language
- TypeScript
- License
- MIT
- Published by
- Community
- Author
- wobsoriano
- Last verified
- Oct 2026
About this project
Oxlint rules written in plain English, answered by TypeSafe Jev. A rule is a yes/no question about a function, a call, a JSX element, or a whole file. Each match is sent to Jev with the question, and the plugin reports an error when the yes-probability clears your cutoff. In CI, set ci: "fail" so a run that could not reach Jev fails instead of passing quietly. Add the plugin and its one rule, jev/ask, to .oxlintrc.json. Your English rules go in the options.
Quoted from the project's README. Read the full README.
Works forJev for Classification
Used inJev for Software & DevTools
- Languages
- TypeScript
Highlights
- Four targets only: whole function, call expression, JSX element or file, with no selector syntax.
- File rules can add a second question to aim editor diagnostics and GitHub annotations at the violation.
- A single request per file carries every match, and answers cache under node_modules keyed by the request.
- Cutoff, timeout, match cap, snippet length and model id are all configurable, with the model defaulting to latest.
Watch out
The README carries an explicit experimental warning. If the key is missing, the request times out or the API errors, the plugin prints one warning and reports nothing for that file, and ci defaults to skip so a run can pass quietly. Answers are cached by request, so retuning a cutoff reuses cached answers while editing a question re-asks the file. Copy reviewed against the repository README on 2026-10-04, not from running it.
Questions about this entry
Short answers drawn from the linked project or page.
By default ci is skip, which warns once and reports nothing for files it could not judge. Set ci to fail so a run that could not reach Jev exits non-zero. Outside CI the plugin always skips.
Not if you care about latency or cost. The oxlint VS Code extension lints as you type, and every keystroke inside a match becomes a paid request that blocks the language server. The README suggests keeping jev/ask out of your editor config and adding it in an overlay for CI and pre-push.
The question wording is the rule, so narrow it. A question like does this send personal data also fires on a legitimate mailer.send, while adding to a log or console does not. Cutoff controls how confident Jev must be before anything is reported.
One initial request per file carries every match, with defaults of 25 matches and 4000-character snippets. Files past 254 nonblank lines trigger range selection and refinement follow-ups that share the same 10000 ms per-file timeout budget.
function reads the whole function, with an arrow or method including its name; call reads the whole call expression; jsx reads the whole element including children; and file reads the whole file. The error underlines the signature line, the whole call, the opening tag or the first line respectively.
A file rule with location sends numbered source and a Choice question, and above 254 nonblank lines Jev selects a range that is refined in follow-up requests with the same full-file context. The violation and location have separate cutoffs, and an uncertain or invalid location keeps the finding on the first line.
Answers cache under node_modules/.cache/oxlint-plugin-jev, keyed by the request. Changing a snippet or a question re-asks that file, while changing a cutoff or an id does not. Location responses cache too, including valid uncertain answers, and malformed location answers are retried on the next run.
More Jev resources like this
1.5kGitHub stars
Open-source platform that puts ACP-compatible agents such as Claude Code, Codex, and Pi inside the team's Slack, Telegram, Discord, and GitHub workflows, with reusable Jev decisions for routing, response gating, and reviewer selection.
Jev Agents & MCP#community#jevbest
488GitHub stars
A coding agent built on pi that hands its non-code decisions — what enters the context, whether a command is safe, whether the work is done — to a small judge model at 35 decision points per turn.
Jev Agents & MCP#community#jevbest
Community
qybaihe/muTypeScript
qybaihe/muTypeScript210GitHub stars
An agent plugin for Pi, Claude Code, Codex CLI and Grok Build that asks Jev two classification questions to decide whether a session sits at a safe compaction boundary, then hints or compacts for you.
Jev Agents & MCP#community#jevbest
572GitHub stars
A CLI plus agent hooks that ask Jev one question per rule in your AGENTS.md on every edit or turn and return a probability, so a violating edit gets repaired inside the same turn. Claude Code, Codex, OpenCode, Pi.
Jev Agents & MCP#community#jevbest
Community
coldteadotai/abideTypeScript
coldteadotai/abideTypeScript147GitHub stars
A local-first desktop agent for macOS that carries work from a conversation through to a reviewable result, split into Home, Cowork and Crew. The part worth a developer's attention is Crew, where Jev suggests an assignee for a single unassigned task and you accept or ignore it.
Jev Agents & MCP#community#jevbest
Community
Foxtailsss-Andy/Anna-AgentTypeScript
Foxtailsss-Andy/Anna-AgentTypeScript116GitHub stars
Stanley is a CLI where you describe a code-review request in plain language and Jev routes it to one of ten bounded workflows. Each workflow is deterministic code that gathers bounded evidence and asks Jev fixed-choice questions per hunk; unmatched requests go to the Pi agent.
Jev Agents & MCP#community#jevbest
Community
devagrawal09/jev-codeTypeScript
devagrawal09/jev-codeTypeScriptFrom the Jev community
Posts from builders shipping with Jev right now.