jevcheck

Turn recurring code-review judgements into testable, repeatable semantic lint rules.

Traditional linters are great at enforcing what can be proved from syntax and types. General-purpose AI review can notice more, but its findings are often difficult to reproduce, calibrate, or enforce consistently. jevcheck sits between them: deterministic code selects a narrow candidate; Jev answers one bounded yes/no question; deterministic policy decides what happens next.

• Start with advisory (shadow) findings; never block a build on an unqualified rule.
• Inspect exactly what would be sent to a model without an API key.
• Test rules against labelled examples, track drift and recall, and promote them to blocking (owned) checks only when the evidence is sound.
• Run the same rule over source files, staged changes, branch diffs, or CI.
• Gate rules on declared Node, .NET, or Go dependencies using manifest-aware projectWhen.hasDependency (no package-manager execution).

jevcheck uses @mhingston5/jev-cli for provider selection. Node.js 20+ is required.

See why it exists: a queue acknowledgement bug

A worker API returns 202 Accepted to a caller once a job has been published to its queue. A refactor catches a publish failure to log it, but still returns success. A reviewer catches the mistake once; the team wants to prevent similar regressions without asking an open-ended AI reviewer to reinterpret its standards on every PR.

The queue acknowledgement walkthrough includes the actual source, a deliberately broken handler, a corrected fixture, a scoped rule, and commands you can run locally. It is a small, production-inspired illustration, not a claim of a real incident or validated model accuracy.

Try the rule without calling a model

From a checkout of this repository:

npm ci
npm run build
node dist/cli.js inspect examples/queue-ack/src/handler.ts \
  --config examples/queue-ack/jevcheck.config.json \
  --rule reliability/no-success-after-publish-failure \
  --verbose