I used Jev to figure out which tests actually need to run after a Git diff

I've been experimenting with Jev recently and wanted to test a pretty simple idea: Most coding agents can modify a repository surprisingly fast now, but then we still run the entire test suite after every change. So I built jev-test-impact. It does: Git diff 👉 static dependency analysis 👉 candidate test files 👉 Jev scores the candidates 👉 run only the selected Vitest/Jest files The important part is that Jev never generates commands or arbitrary test paths. It can only choose from tests that were discovered locally. There's also a completely local --static mode so I can benchmark: full suite vs static analysis vs static + Jev I'm especially interested in measuring regression recall, rather than just publishing some ridiculous "99% fewer tests" number while silently missing bugs. I'd love to test this against larger real-world TypeScript repos. I'm also curious, what would make you trust something like this enough to use it in CI?