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

How to find the code behind a behavior before an agent edits it with Jevgrep

Ask a repository question and get files, leads, and source excerpts to start an unfamiliar change.

Credentials. Eligible source from the search root is sent to the provider you selected, and the credential filter is best-effort, so choose a root you intend to share.

Who it is forA developer new to a codebase who has been asked to change a behavior but does not know which files implement it.

The problemCoding agents spend part of every unfamiliar task finding the right files, and the developer lacks a starting point.

The outcomeA stdout summary with a compact file list, selected source with line references, and declaration and call locations to guide the change.

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 npm install -g @dzhng/jevgrep to install the CLI.
  2. Run jg auth and choose your provider and key.
  3. Run jg skill from the project where your agent works.
  4. Run jg "How are telemetry events recorded and sent?" ./my-project with your own question and path.

Prompt for your agent

Use the jevgrep skill in this repository to run `jg` with the question "<question about the behavior>" against <target path>. Report the files, line references, and source excerpts it returns, and confirm each cited file exists before you propose any edit.

Caveat. Jevgrep returns evidence for the agent to judge, not a generated answer or a guarantee that every relevant file was found.

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