GitDiagram is an open-source micro dev-tool that I made this past week
Given any public GitHub repository it generates diagrams in Mermaid.js with Claude 3.5 Sonnet Try it out for free at https://gitdiagram.com
I extract information from the file tree and README for details and interactivity (you can click components to be taken to relevant files and directories)
Also, you can replace "hub" with "diagram" in any repository URL to access its diagram
I created this because I wanted to contribute to open-source projects but quickly realized their codebases are too massive for me to dig through manually, so this helps me get started
I do still plan on adding other features like private repository access if that becomes a thing people want
This project was heavily inspired by https://gitingest.com/ so make sure to check that out as well!
Hopefully this tool can help you and feedback is always welcome!
Nice idea so far, I think it'd be nice to have some documentation expounding on the use case more (i.e. groking a large codebase). Look forward to seeing the future iterations!
This is such a neat tool! As someone who often struggles to navigate large codebases, being able to visualize everything in an interactive diagram sounds super helpful. Love how simple it is to use—just swapping "hub" with "diagram" in the URL is genius. Excited to try it out for some open-source contributions! Congrats on the launch! 🚀
A product I know about from Hacker News. Visualization will help developers quickly read, understand and memorize the hierarchy of codebases.
Good going, Ahmed!
😸 Really cool! Would love if it could be exported to some kind of markdown output, so It could be added to readme.md docs? And maybe add support for BYO OpenAI key, to offset cost for you?
I liked it, honestly, but I just played with the repos. But didn't analyze the outcome. Just visualizing.
To be fair, for the first shot I think this is absolutely great. Documenting work and and making it understandable for outsiders is always hard, so having an easy option to do so is amazing!
I think your tool would benefit from having a few more "deterministic" internal steps or improved prompting. I tested it on: https://gitdiagram.com/mdx-edito... Which to be fair is not the easiest code base to understand (at least for me). It did a great job at analyzing the components and the "semantic" value behind them, but it's missing some blocks that should have been there and vice versa.
It's a great start, I think there's a good chance that you can quickly iterate upon it to make it better very fast.
I like the idea, but a funny thing happened as I tried it out:
For one of my (still quiet empty) public repos, the model hallucinated and added a bunch of components and layers that don't exist 😂
The repo only has a License and Readme.md, feel free to try it out with the repo: https://github.com/juliangoetze/...
