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 2 of 2

  • Pi guardrails on pi-typesafe that steer the agent: Jev checks rule breaks, irreversible actions, stuck loops and unverified done claims.

    HookbetaTypeScript
  • GitHub Action that compiles .jev.yml rules into Jev questions and fails, comments on or passes a PR based on the numbers.

    ProjectbetaTypeScript
  • Ruff-style prose linter whose semantic rules each ask Jev a yes/no question about a paragraph, title or section, with tunable thresholds.

    ProjectbetaPython
  • Go linter whose rules are plain-English questions: static analysis picks nodes, Jev answers a Noul about each one.

    CLIbetaGo
  • Node tool that crosschecks a folder of Markdown notes for contradictions and repeats, and ranks notes by any question, using Jev.

    ProjectbetaJavaScript
  • CLI and agent skill that checks every line of a document against every rule with Jev and outputs flags for an AI agent to fix.

    Agent skillbetaTypeScript
  • Prose linter for AI writing tells: regex handles 18, Jev judges 15 as Nouls in one call, shipped as a Claude Code Stop hook.

    HookbetaPython
  • Prose linter with local regex rules and Jev judgment rules per paragraph, as CLI, pre-commit hook, GitHub Action and Claude Code skill.

    CLIbetaTypeScript
  • CLI design and copy linter: mechanical checks block commits, while fuzzy taste checks go to Jev for probability-scored review notes.

    CLIbetaTypeScript
  • Linter that scores code comments on five heuristics with Jev and fails CI when comments fall below thresholds.

    LibrarybetaPython
  • Offline linter and agent skill that checks Jev requests for badly designed questions before they come back confidently wrong.

    Agent skillbetaTypeScript
  • Chinese controlled-writing agent skill for technical reports with nine rules, using static checks plus a Jev semantic gate for certainty.

    Agent skillbeta
  • Semantic ArkUI linter for coding agents: a fact extractor finds candidate state bugs and a System One model judges each one.

    ProjectprototypeTypeScript
  • Dependency-light Go linter that applies natural-language rules to code and documents using decision models like Jev or Clef.

    ProjectprototypeGo
  • Claude Code plugin for Rust review: compiler and Clippy facts first, Jev triages semantic risks, Claude reviews and Jev verifies findings.

    ProjectprototypeRust
  • VS Code extension that asks Jev a yes/no question ('is this ok?') about each line you edit and marks it thumbs up or down.

    ProjectprototypeTypeScript
  • Oxlint plugin where lint rules are plain-English yes/no questions about code that Jev answers, reporting matches above a cutoff.

    PluginprototypeTypeScript
  • Small eval that uses Jev to judge whether shadcn-ui/lint findings are correct and whether each message says what to change.

    ProjectresearchJavaScript
  • Repository describing a Roblox Studio instance reviewer using typed Jev criteria with citations; README is mostly marketing.

    Project
  • Supercov★ 154

    Coverage, security and quality CLI where Jev answers yes/no property questions per file so agents know what to fix first.

    CLIproductionRust
  • SysOneScript language, Go System One client, semlint semantic code checks and a VS Code Studio for building with Jev judgments.

    LibrarybetaGo
  • MoonBit and TypeScript Jev playground: gomoku, shell-command risk gate, ESLint plugin, a tiny Jev-condition language and measured reports.

    AppresearchMoonBit
  • Local MCP server giving Claude Code, Codex, Cursor and OpenCode per-dimension Jev quality scores on their code while they work.

    ServicebetaTypeScript
  • Semantic linter that evaluates files against plain-English JSON rule packs in one /v1/systemone pass, locally with Kev or remotely with Jev.

    ModelbetaPython