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

How to find repository files by meaning, not keywords with Awesome Jev

Score live repository files and code ranges with Jev probabilities, without an index.

Who it is forA developer entering an unfamiliar codebase who cannot guess the exact function or variable names.

The problemKeyword search misses files that do the right job under different names, and building an embedding index takes setup.

The outcomeA ranked set of files and code ranges that match a plain-language description, read directly from the working tree.

What you need first

  • Access to Jev through the TypeSafe early-access entry point at typesafe.ai
  • A small labeled sample of your own data to check Jev answers before relying on them

Steps

  1. Open the jegrep repository at github.com/can1357/jegrep and install it following its README.
  2. Describe the behavior you are looking for in one plain sentence.
  3. Run jegrep against the repository directory.
  4. Open the top-scored files and ranges and confirm they match the description.
  5. Refine the query wording and rerun if the top results are off target.

Prompt for your agent

Use the jegrep tool at github.com/can1357/jegrep on <repository path> with the query <plain-language description>. Report the top ten files and ranges with their probabilities. Verify the top three by reading the code.

Caveat. The probabilities rank candidates for reading, so confirm each hit in the source rather than treating scores as proof.

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