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

How to find where a feature lives in a large codebase or file with Quicksilver

Rank files by relevance to a question, or find the lines in a huge file that match it.

Who it is forA developer joining an unfamiliar codebase or a large module who needs to find the code behind a feature.

The problemClaude spends many tokens opening candidate files to figure out which one implements the feature.

The outcomeClaude gets the top ranked files or matching line numbers; the benchmark's where-is-X task hit the right answer in the top 3 for 10 of 10 questions with 91% fewer Claude tokens.

What you need first

  • Claude Code installed
  • Node 18 or later
  • A Jev key from console.typesafe.ai
  • Content you are allowed to send to TypeSafe's API

Steps

  1. Get a Jev key at console.typesafe.ai and run npx github:UditAkhourii/quicksilver.
  2. Restart Claude Code.
  3. Run qs rank "where do we issue refunds?" src --top 5 and replace the question and folder with yours. (inferred, check the README)
  4. For one very large file, run qs find "the retry backoff logic" huge_module.py to get matching lines. (inferred, check the README)
  5. Open the top results in Claude and confirm the match before editing anything.

Prompt for your agent

Using the repo UditAkhourii/quicksilver, run qs rank with the question "<feature question>" against <target-directory> with --top 5. Return the ranked file paths and say which one most likely implements the feature. Verify that the output lists no more than five files.

Caveat. Quicksilver does not replace grep for exact text searches, so use plain search when you know the exact string you need.

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