jevq

jq | jevq | jq. jq handles structure; jevq reads one JSON value per line from stdin, asks Jev (a TypeSafe System One model) a yes/no question about each, and passes through the yeses. QUESTION is a yes/no claim about the current value, not a search query.

Install

uv tool install --editable .
export TYPESAFE_API_KEY=...

scripts/reinstall-cli.sh forces a rebuild (--dry-run, --no-editable, --skip-smoke).

Options

jevq [options] QUESTION reads JSONL on stdin. QUESTION is required unless --pass.

--score and --pass are mutually exclusive. A flag beats its env var.

Environment

Use cases

jq -c '.[] | select(.status == "open")' samples/tickets.json |
  jevq "the customer is asking for a refund" |
  jq -c '{id, subject}'

Open tickets asking for money back, printed as {id, subject}.

jq -c 'select(.level == "error")' samples/app.ndjson |
  jevq "this error is caused by a network timeout, not a bug in our code"

Error log lines that look like a timeout rather than a code bug.

gh api 'repos/itchyny/gojq/issues?state=open&per_page=100' |
  jq -c '.[] | select(.pull_request | not) | {number, title, body}' |
  jevq --score "reports a crash or wrong output, not a feature request" |
  jq -rs 'sort_by(-.score) | .[:5][] | .value | "\(.number)\t\(.title)"'

The five most bug-like open issues, as number<TAB>title.

More examples: docs/examples.md

Full contract (output rules, exit codes, HTTP, retries): docs/jevq.md

Testing

uv run pytest -q
bash tests/samples/run.sh

JEVQ_LIVE=1 TYPESAFE_API_KEY=... bash tests/samples/run.sh runs the sample pipes live.

Not supported in v1: --path, a jev() builtin, concurrency, caching.