OverviewCopy Anchor Link

ev-grep finds source files from a description of their behavior. Use it to locate an implementation or narrow a code review.

Install ev-grep and set an API key before running these searches.

Find an implementationCopy Anchor Link

Locate retry logic without knowing the function names:

ev-grep 'Retries failed HTTP requests' src/

Check error handlingCopy Anchor Link

Find code that hides a database failure:

ev-grep 'Catches a database failure and returns an empty result' src/

Illustrative terminal output:

src/users.py     match
src/actions.py   uncertain

Open the matching files to check them. Keep uncertain files in the review: they may need more context. Nonmatches are omitted from terminal output; --json includes every assessment.

Narrow a reviewCopy Anchor Link

Look for database writes in a few files you're reviewing, or in the lines that changed:

ev-grep 'Writes to the database' src/users.py src/actions.py:40-72

Each assessment reads the full file, even when a range narrows it. It does not compare revisions or establish whether a change introduced a problem. Use with other tools gets changed lines from git diff.

Preview what gets sentCopy Anchor Link

ev-grep 'Retries failed HTTP requests' src/ --dry-run

A dry run lists files and sizes without making requests. During a search, the query, path, and contents of each selected file go to Jev through your chosen provider. Requests use your API key and may incur charges.

See Concepts for file context and decisions, CLI for filters, ranges, and query files, Use with other tools for pipelines, or Output for JSON and exit codes. Model results can be wrong; use them to decide where to look.