Every developer has felt it. You join a new project, someone points you at a GitHub repo, and says "just explore the code." Two hours later you're still reading files one by one, trying to figure out which file talks to which, where the actual logic lives, and why there are four different things called "manager."
I got tired of that. So I built something about it.
The idea was simple. The execution wasn't.
Give it a GitHub URL. It clones the repo, figures out the architecture, and hands you an interactive dependency graph with a natural-language summary of how everything fits together.
Simple idea. Except — how do you actually teach a machine to understand a codebase the way a senior engineer would?
