Jev directory
CommunityJev Tools & CLIs
Jev Test Filter — npmjs.com
Command-line tool that reads a git diff, asks Jev how much the change can alter each test's outcome, and prints filter arguments for vitest, jest, node --test, bun test, Playwright, cargo test, or go test.
- Reading time
- 2 min
- Published by
- Community
- Added
- Nov 2026
This is one of several Jev listings for the same project. The canonical entry is Jev Test Filter — mizchi.
Highlights
- Supports vitest, jest, node --test, bun test, Playwright, cargo test, and go test.
- Uses one shared state (the diff) and one question per test, with no agent loop and no file reading by the model.
- Requires Node 24 or newer, git, and a TypeSafe API key; rust and go formats also need cargo and go on PATH.
- --exec appends selection arguments to your command through spawn, with no shell in between.
- --verify-snapshots labels changed .snap files plausible, review, or unknown without editing snapshots or running tests.
Questions about this entry
Short answers drawn from the linked project or page.
Install with pnpm add -D jev-test-filter, or run it without installing via npx jev-test-filter --base main --exec -- vitest run. It requires Node 24 or newer, git, and a TypeSafe API key. The rust and go formats additionally need cargo and go on the PATH.
It emits filter arguments for vitest, jest, node --test, bun test, Playwright, cargo test, and go test, so the run covers the tests the change could plausibly break instead of all of them.
Everything after --exec -- is your command, and the selection arguments are appended to it. They go straight to spawn with no shell in between, so nothing can be re-split or re-quoted, and the command's exit code becomes the tool's exit code.
It reports framework, mode, argv, fallback, selected and total counts, and spend (calls, input and output tokens, milliseconds, retries, rate limits, and usd), plus every test with its file, name, line, selected flag, reason, score, and confidence.
It sends one shared state (the diff) and one question per test in a single round trip. Tests whose own body sits inside the diff are marked touched and cost no tokens; others are kept or dropped by score and confidence.
No. Installing the skill does not install the command, and you want both. Add the skill with npx skills add mizchi/jev-test-filter for Claude Code, Codex, Cursor and similar agents; the Claude Code plugin adds the same skill plus a /filter-tests command.
It is advisory and does not fail CI on a suspicious update. It reads the working-tree diff by default, does not edit snapshots or run tests, ignores image snapshots, and treats each .snap file as one question, so a suspicious entry marks the whole file for review.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
YouTube: Ray Amjad puts Jev inside an agentic coding loop and looks at what it costs to run.
YouTube: RoboNuggets puts Jev to work inside Claude Code.
X: Decision outputs in Grep
Hacker News: jevmem keeps Claude Code project memory by asking Jev which turns are worth saving.
avinashjetwani61 pointsJevmem – automatic project memory for Claude Code, built on JevRead the thread on Hacker NewsFrom 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.