pi-jev-guard
Pi extension that checks proposed code edits against repository Markdown rules with Jev, reporting rule text and line ranges.
Overview
Pi Jev Guard checks proposed code edits against Markdown rules using TypeSafe Jev before Pi writes them, returning the exact instruction text and source line range for each detected violation. The default informative mode reports findings without blocking; enforcement mode blocks detected violations in code selected for review.
The guard selects one instruction root when the policy loads, by default the Git repository root containing Pi's working directory; edits outside that root are skipped without a Jev request and permitted in both modes, and /jev status shows the active root. The package ships a generic starter policy with no organisation-specific rules, does not read .env files, and requires TYPESAFE_API_KEY in Pi's environment. The README describes it as a semantic review aid, not a replacement for tests, linters or a security sandbox. It requires Pi 0.85.1+ and Node 22.19+.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Yes / no | Does this proposed edit violate this Markdown rule? | yes · no |
How it works
- Load the policy and instruction root.
- Before a write, send the proposed content and rules to Jev.
- Report or block violations with rule text and line range.
- Skip edits outside the active root.
Strengths
- Cites the exact rule and lines violated.
- Informative mode for safe adoption.
- Clear scoping rules.
Caveats
- Not a substitute for tests or linters.
- Cross-repository edits are skipped by default.
Getting started
pi install git:github.com/Reindeer-AI/pi-jev-guard and set TYPESAFE_API_KEY in Pi's environment.At a glance
- Type
- Project
- Status
- beta
- Language
- TypeScript
- Runtime
- Pi extension
- Has code
- yes
Use cases and integrations
How curated lists describe it
Check Pi code edits against repository Markdown rules with TypeSafe Jev
logicrw/awesome-jev-projects
Frequently asked questions
Does it block edits by default?
No, informative mode reports without blocking; enforcement mode blocks.
What about files in other repositories?
They are skipped without review unless you widen the instruction root.
Where do rules come from?
Markdown instruction files in your repository.
Related projects
Coding-agent hook that asks Jev one yes/no per project rule on every edit or turn and makes the agent fix any violation.
HookbetaTypeScriptAdvisor for coding agents: git and Stop hooks flag test tampering, secrets and skipped hooks, with optional Jev review findings.
HookbetaFuzzy linter CLI that checks a code tree against plain-language rules in one markdown file, judged by Jev via a swappable interface.
ProjectbetaTypeScriptSemantic code linter that reads each method with its callers and callees and asks decision models about defects, kind, line and severity.
CLIbetaTypeScriptLean Pi supervisor: zero-token regex guardrails, done-check verification, per-turn routing and a Jev/Clef semantic slop gate on diffs.
ProjectbetaTypeScriptAdvisory Jev sidecar for Pi: four pre-flight hazard checks before bash/write/edit and four diff-quality checks after edits.
PluginbetaTypeScript