Oxlint rules written in plain English and answered by Jev.
@wobsorianoEach rule is a yes-or-no question about a function, a call, a JSX element or a whole file. Every match is sent to Jev with the question, and the linter reports an error when the answer crosses your threshold.
Add it to your Oxlint config like any other plugin. In CI you can make a run fail if Jev cannot be reached, rather than passing quietly. Experimental.
A single interface across dozens of AI providers, with a calibrated decide call powered by Jev for the routing and gating choices text generation was never meant to make.
Jev
TypeScript
Node.jsTrims long command output with Jev before Claude Code reads it, so later turns carry less noise.
JevTypeScript
Claude CodeRoute web requests by meaning instead of by path, in the Hono framework.
JevTypeScript
HonoContinuous quality scores for code written by AI agents, from a local MCP plugin powered by Jev.
JevTypeScript
MCPKeep the skills list out of every Pi request and let Jev pick the skills each task needs.
JevTypeScriptFast Jev compaction for the Pi coding agent: prune stale tool history, keep every word of the conversation.
JevTypeScript
