Skip to content

Jev directory

Pr Sieve

A GitHub Action that treats .jev.yml as a semantic linter for pull requests: each rule is a typed Jev question (Noul, Choice or Score) and the check fails, comments or passes from those numbers. It writes no reviews, suggests no patches and approves nothing.
Stars
1
Language
TypeScript
License
MIT
Reading time
3 min
Published by
Community
Author
thestral12
Last verified
Oct 2026

thestral12/pr-sieve

User repository on GitHub

View on GitHub

Semantic PR gate: .jev.yml rules as TypeSafe Jev questions. Not a review bot.

Forks
0
Last pushed
Updated Sep 2026

Repo stats from the GitHub API, cached Oct 2026.

Highlights

  • Policy is read from the base ref, so a PR cannot rewrite the gate that judges it.
  • Secret-shaped strings such as AWS AKIA keys and private-key armor fail in code with no Jev call; everything else is one systemOne batch capped at 12 questions.
  • Reasons are templates like missing_tests 0.87 meets 0.80 and fail, not generated prose; a clean run still posts a comment reading clean.
  • Sits closest to check-risk (risk score) and is explicitly not jev-review (review, approve, dashboard).
  • TypeSafe 429, 5xx or timeout yields neutral with sieve degraded; fork PRs without a key skip as neutral; a same-repo missing key is a setup failure.

Quickstart

bash
pnpm install
pnpm sieve eval --live
pnpm sieve doctor

Watch out

Copy reviewed against the repo README on 2026-10-15; it documents example rules (looks_like_secret, missing_tests, touches_auth, change_kind) but no full rules reference or benchmarks, and the local eval is described as a mocked gold bar unless run with --live. Pin a commit SHA, not a tag: tags move.

Questions about this entry

Short answers drawn from the linked project or page.

From the Jev guides

Original write-ups on what this entry is for.

From the Jev AI model community

Posts from builders shipping with Jev right now.

Follow @typesafeai