No reviews yetBe the first to leave a review for RepoDoc
Maker
📌
RepoDoc was built to make code easier to explore, understand, and share.
It turns GitHub repositories into clear, visual documentation automatically.
Feedback and ideas are very welcome.
Report
💡 Bright idea
Gave this a go and thought it was pretty cool. It auto-detected the correct documentation template to use.
The value-add I see here is that it produced useful Mermaid diagrams for architecture and data flow for my full stack app, something Claude wouldn't do unless I specifically asked for it. The output is also in a much more readable language than AI emoji slop.
I would like to see more generated sections in general though, even if they're not necessarily engineering-related. But maybe that's my preference as a verbose README enjoyer. For example, I have a license file at the root but that wasn't included in the README. I would also like to see more "presets" or options for me to configure how exactly I want the repo to look. (For example, a tone selector, sections to include, verbosity scale, etc).
I'm curious, what is this app's strategy for analyzing the context it retrieves from my repo? Excited to see how this evolves.
Gave this a go and thought it was pretty cool. It auto-detected the correct documentation template to use.
The value-add I see here is that it produced useful Mermaid diagrams for architecture and data flow for my full stack app, something Claude wouldn't do unless I specifically asked for it. The output is also in a much more readable language than AI emoji slop.
I would like to see more generated sections in general though, even if they're not necessarily engineering-related. But maybe that's my preference as a verbose README enjoyer. For example, I have a license file at the root but that wasn't included in the README. I would also like to see more "presets" or options for me to configure how exactly I want the repo to look. (For example, a tone selector, sections to include, verbosity scale, etc).
I'm curious, what is this app's strategy for analyzing the context it retrieves from my repo? Excited to see how this evolves.