Project
RepoTwin
TESTINGA repo intelligence twin that maps, indexes, embeds and answers questions across an entire codebase.
- Shipped
- Stack
- Python · Tree-sitter · SQLite · Ollama
- Source
- https://github.com/MistaJoka/repotwin
- Built
- Wrote the incremental indexer, the tree-sitter symbol extractor, and the hybrid keyword-plus-vector retrieval layer.
- Model
- Claude Opus 5
What it is
A local service that keeps a live model of a codebase — files, symbols, call edges, and embeddings — and answers questions against it without sending the source anywhere.
Why
Every “chat with your repo” tool I tried either re-indexed from scratch on every run or shipped the code to someone else’s GPU. I wanted neither.
Where it is
Indexing and retrieval work. The answer quality is good on “where is X defined” and mediocre on “why is X built this way” — which is the gap between a symbol graph and actual intent. That’s the next problem.