Skip to content

Code quality and linting with decision models

Fuzzy lint rules written in English, team-convention checks and file-level quality scores that tell a coding agent what to fix first.

54 public projects · page 1 of 2

  • Rust code-review gate asking Jev small typed questions about functions and tests, failing CI only on rules measured 80% right.

    CLIproductionRust
  • Coding-agent hook that asks Jev one yes/no per project rule on every edit or turn and makes the agent fix any violation.

    HookbetaTypeScript
  • PR reviewer where Jev answers a Clean Code question set for every changed file and a writing model turns the verdicts into review prose.

    ServicebetaTypeScript
  • Advisor for coding agents: git and Stop hooks flag test tampering, secrets and skipped hooks, with optional Jev review findings.

    Hookbeta
  • CLI that uses Jev to score JS/TS code comments for accuracy and usefulness and lists the weakest first.

    ProjectbetaTypeScript
  • CLI that asks one yes/no question of every function in a codebase with Jev and ranks them by probability: grep whose pattern is a question.

    CLIbetaPython
  • Read-only Go CLI that checks files against your plain-language code rules with Jev, locally or in CI.

    CLIbetaGo
  • CLI and agent commands auditing a git diff against YAML standards packs, scoring each hunk with Jev so agents fix only flags.

    Agent skillbetaTypeScript
  • Claude Code plugin that checks every reply and file edit against your CLAUDE.md rules with one Jev yes/no per rule.

    PluginbetaTypeScript
  • Claude Code plugin that moves CLAUDE.md rules into hooks, denying rule-breaking edits and unasked deploys via Jev probabilities.

    ProjectbetaTypeScript
  • Fuzzy linter hook for Claude Code and Codex where Jev checks each written file against team rules and reports violations at edit time.

    HookbetaTypeScript
  • Natural-language linter combining ast-grep selectors with Jev to catch misleading names, stale comments and tests that miss their claims.

    ProjectbetaTypeScript
  • GitHub Action that reviews repository files against your yes/no questions with Jev and passes only when every answer meets its threshold.

    ProjectbetaTypeScript
  • GitHub Action where Jev rates each PR across 19 software-quality dimensions, gates on thresholds and logs to a RawTree dashboard.

    AppbetaTypeScript
  • Turns AGENTS.md preferences into a Jev-powered semantic linter for diffs, staged files or PRs, feeding findings back to coding agents.

    ProjectbetaTypeScript
  • Neovim plugin that asks every function in the buffer a plain-language question with Jev and lists hits in quickfix ranked by probability.

    PluginbetaLua
  • Node quality gate that scores each diff, commit message and doc set with three Jev Score lenses and a security Noul.

    CLIbetaTypeScript
  • Cheap Jev checks beside a Claude coding session: per-function code rules, doc contradiction checks and context retrieval.

    ProjectbetaPython
  • Linter for Jev queries that flags question and state wording the model is documented to handle badly, before you pay.

    ProjectbetaPHP
  • Semantic lint rules as yes/no questions to Jev, for review issues like logged secrets or unbounded retries that ESLint cannot express.

    ProjectbetaTypeScript
  • Semantic linter that checks each source file against plain-English conventions and reports Jev's probability of a violation.

    PluginbetaTypeScript
  • Go linter that extracts code units with Tree-sitter and asks a decision model whether each passes a plain-language rule.

    ProjectbetaGo
  • CLI and MCP tool that finds hard-coded judgment calls in your code, scores how well Jev fits, and replaces strong fits with a fallback.

    ProjectbetaTypeScript
  • Turns freeform Markdown engineering rules into PR checks, judging changed lines with Jev or other Decisions-API providers.

    ProjectbetaTypeScript
  • Single-binary linter whose rules are plain-language questions in YAML, asked of each file as a Jev yes/no judgment.

    ProjectbetaRust
  • Fuzzy linter CLI that checks a code tree against plain-language rules in one markdown file, judged by Jev via a swappable interface.

    ProjectbetaTypeScript
  • Semantic code linter that reads each method with its callers and callees and asks decision models about defects, kind, line and severity.

    CLIbetaTypeScript
  • Lean Pi supervisor: zero-token regex guardrails, done-check verification, per-turn routing and a Jev/Clef semantic slop gate on diffs.

    ProjectbetaTypeScript
  • Pi extension that checks proposed code edits against repository Markdown rules with Jev, reporting rule text and line ranges.

    ProjectbetaTypeScript
  • Advisory Jev sidecar for Pi: four pre-flight hazard checks before bash/write/edit and four diff-quality checks after edits.

    PluginbetaTypeScript

Related categories

Related coding agents