Interesting approach. I built something similar <a href="https://github.com/nilbuild/diffity" rel="nofollow">https://github.com/nilbuild/diffity</a> to understand unknown codebases. The difference is it gives you the interactive walk-through with mermaid diagrams, guiding you through the feature or part of the codebase that you're looking at.
Did anyone actually use this on a complex codebase and have any kind of intuition for it ?<p>Like, having looked at the demo, it feels less intuitive and extra complex than going through the codebase myself with tmux + codex + reading it myself.
I think for you to understand the codebase, it should be easier to interact without. This seems to introduce way too many steps to interact with the codebase
is this like Obsidian's graph view? Looks pretty/makes cool screenshots but has no actual value and is just cumbersome to use? (btw, this isn't meant to be a mean comment, just a question after looking at the output.)
What evidence is there that this makes any difference at all? There are a gazillion (and one) codebase understanding solutions using knowledge graphs. How do I know if it's any good compared to just using Codex or Claude Code?
[flagged]