Repo Search for Coding Agents
Real Source Code
Answers the Question
Clone any GitHub repo into a persistent sandbox, then let your agent search the real code instead of recalling it from memory.
AI agents answer questions about libraries from memory. Memory is often wrong, outdated, or invented outright.
The external problem
You ask how an external library or framework actually implements something, and the agent answers from training data instead of opening the repo.
The internal problem
The answer sounds confident and specific, right up until it turns out to describe a different version, or a method that doesn’t exist in the codebase at all.
What's at stake
Time spent chasing an answer that was never true, or code shipped on a wrong assumption about how a dependency actually behaves.
Three steps: confirm the repo, clone it, verify by reading.
Give it a repo name or URL, and it clones, syncs, and searches before it answers.
Find & Confirm
Give a full GitHub URL, or just a name. If it’s only a name, the skill searches the web to confirm the exact repository before cloning anything.
Clone & Sync
The repo is shallow-cloned into a persistent, read-only sandbox. Every run resets it to match the remote’s current default branch, so you’re always searching current code.
Search & Verify
Haiku subagents comb the codebase in parallel to find the relevant files. Every file they point to gets read directly before it factors into the answer.
Use it now. It's free.
Works on all platforms. Pick yours and get set up in under a minute.
Download & upload in 60 seconds
One click downloads the zip and opens Claude.ai.
Click below — the zip downloads and Claude.ai opens.
Click the + button in the skills column on the left.
Select Create a skill.
Select Upload a skill and upload the zip.
Start your repo search session by running /estack-repo-search.
Repo Search ships in E-Stack, a set of 20 free skills installed by one command. See the whole stack.