Integrations
jev-ci-pathfinder lets Jev decide which optional CI jobs a change actually needs, one allowlisted job at a time. Always-on jobs, path rules, and dependency closure never leave code, and when Jev is unavailable the action runs its configured conservative set rather than guessing.
Screenshot unavailable. Open the experiment ↗
One boolean question per job comes back as a typed selection, with low-confidence answers marked provisional under policy instead of turning into silent skips. The README also discloses the detail most such tools hide: dry-run mode still spends provider calls. Config guardrails get real treatment — CODEOWNERS, branch protection, and a fail policy are all documented.
To reduce repeated work after changes to your app, start with the example list of testing tasks. A developer can mark vital ones to always run. The tool sends file names and task details to an outside AI service to choose the rest. If the answer is unusable, the default runs the full list.