Hi, Malik from Adrenaline here!<p>We built a system to auto generate interactive system diagrams to help document and understand any codebase (useadrenaline.com).<p>Diagrams are often the most useful medium of communicating how code works. But creating diagrams suffers from the same problem as documentation - it’s a pain to set up, and then quickly becomes out of date.<p>The idea of using diagrams to explain code has been around for a while, but tools to auto-generate these visuals purely from static analysis are often way too busy.
So we built Adrenaline - it uses a mix of static analysis to build up a callgraph, with LLMs to organize the different methods and classes into more cohesive subgraph ‘topics’.<p>With this approach, we automatically generate diagrams showing how a repo works, updating as the codebase changes. We built it because, honestly, we were tired of spending hours creating diagrams that were obsolete within weeks. Plus, with how complex systems are nowadays, it's become a real headache to keep everyone on the same page about how pieces of a service fit together. Adrenaline takes care of that, making it super easy to create and share explanations for any repo. It's like having a constantly updated map of your codebase. We're hoping it'll save devs a ton of time and reduce those annoying misunderstandings that come from outdated docs.<p>You can try it out right now – it’s free for any open-source repo! Let me know what you think.