I’ve been using Claude Code more seriously on bigger repos, and the biggest pain point for me is not that Claude can’t write code. It usually can. The annoying part is that every new task starts with this same “repo archaeology” loop: inspect the project open a bunch of files search imports check callers look for tests understand the same module boundaries again finally edit something Then the next task starts, and it does a lot of that again. On small projects, this is fine. On a large repo, it feels like I’m paying tokens for Claude to rebuild the same mental map over and over. So I built RepoScry . RepoScry creates a local graph/map of your codebase and generates a small task-specific Markdown context file before Claude starts editing. The idea is: Example: reposcry init reposcry index --no-semantic reposcry context “fix login session expiry bug” \ –strict \ –budget 20000 \ –format markdown > .reposcry/AI_CONTEXT.md Then in Claude Code, I say: Read .reposcry/AI_CONTEXT.md first. Use it as the repo map for this task. Do not start broad repo exploration unless the context is clearly insufficient. The context pack can include: relevant files symbols dependencies reverse dependencies affected flows tests that may matter validation commands After Claude edits, I can update only changed files: reposcry-update --changed --base main reposcry validate main HEAD This is not meant to replace Claude Code. It is more like a pre-task repo memory layer, so Claude starts with better structure instead of wandering through the repo from zero every time. Repo: https://github.com/zibouddd/reposcry submitted by /u/raaaaapl
Originally posted by u/raaaaapl on r/ClaudeCode