DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check which files a search will send before running it with Jevgrep

Count the files under a root and exclude paths so only intended source reaches the provider.

Credentials. The README says the sensitive-content filter is best-effort and not redaction, so review the file list yourself before searching.

Who it is forA team lead or security-minded developer who must confirm what source leaves the machine before a search runs.

The problemSearches send eligible source to Jev, and automatic filtering is best-effort, so the scope needs checking first.

The outcomeA per-directory file count and a narrower search that skips generated or test paths, reducing what is sent to the provider.

What you need first

  • Node.js 22+ on macOS, Linux, or Windows
  • An API key for Vercel AI Gateway, TypeSafe, OpenRouter, OpenCode Zen, or a custom TypeSafe-compatible endpoint
  • A local checkout of the repository you want to search
  • A coding agent such as Claude Code or Codex to run the installed skill

Steps

  1. Run jg files [root] on the directory you plan to search, using your own path in place of [root].
  2. Review the counts grouped by top-level directory.
  3. Add --exclude with a gitignore pattern relative to the root, for example --exclude 'src/generated/'.
  4. Run jg "<your question>" <root> with the same exclusions applied. (inferred, check the README)

Prompt for your agent

For the repository at <target path>, run `jg files <target path>` and summarize the file counts by top-level directory. Then propose `--exclude` patterns for generated or sensitive paths and confirm the counts drop before any search is run.

Caveat. `jg files` needs no provider key or network request, but it only counts files and does not prove that no sensitive content remains in the searched paths.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page