Gate shell pipelines and CI steps on what the text means
Pipe text into a CLI that checks it with Jev and returns an exit code, so scripts and CI steps run only when it passes.
The use case
Developers and ops staff often want a script step that depends on meaning: only alert if this log line describes a real outage, only run the release note job if the changelog mentions a breaking change. These command-line tools take text on stdin, put a yes/no or match question to Jev, and return a stable exit code or the filtered lines, so they slot into shell pipelines, cron jobs and CI. One also searches files by meaning across languages. An engineer reviews the threshold, and nothing destructive should run on a model's yes alone.
Example workflow
- Install the CLI in the CI image or on the server
- Pipe text or JSONL into it with a yes/no question
- Use the exit code to gate the next step in GitHub Actions or cron
- Set a conservative probability threshold
- Review gated runs and misses monthly
Tools
- Jev (TypeSafe AI)
- GitHub Actions
- cron
- Bash
Risks and guardrails
- Destructive commands gated on a model answer are dangerous
- API outages can block pipelines unless handled
- Thresholds that are too low let noise through
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- SemDecide by Sharvil Saxena on Made with Jev: madewithjev.com/builds/semdecide
- SemDecide: original post or repo by Sharvil Saxena: github.com/sharziki/semdecide
- jevgate by Gordon Brander on Made with Jev: madewithjev.com/builds/jevgate
- jevgate: original post or repo by Gordon Brander: github.com/gordonbrander/jevgate
- sys1grep by uehaj on Made with Jev: madewithjev.com/builds/sys1grep
- sys1grep: original post or repo by uehaj: github.com/uehaj/sys1grep