Jev Lint

A Go linter that checks code against plain-language rules: Tree-sitter extracts code units, then each one is sent to Jev or another configured decision provider to decide whether it passes, with caching and eval fixtures.

A linter whose rules are plain-English yes/no questions about code — secrets in logs, retry loops that run forever, leaked error messages — answered by TypeSafe's Jev as calibrated probabilities, with output shaped like any other linter.

Runs cheap Jev checks beside a Claude coding session: code rule lint against project rules, doc consistency checks, and context retrieval, re-checking only changed code and recording every verdict so it is not paid for twice.

A semantic linting CLI that parses a repository into a method-level call graph, then asks Jev to flag likely defects and check rules written in plain English.

An ast-grep semantic linter where each rule is one natural-language question judged by Jev: 98 rules flag name/body drift, stale comments, weak tests, quiet failures, and commits whose diffs contradict their messages.