Original Summary

Hi everyone, I'm Alessandro and I've been building doc0, which turns a codebase into a wiki that stays in sync as the code changes. Before going further, I want to know whether the output is actually good, so I generated wikis for a few open-source projects and I'm asking feedback on the actual quality of the output. How it differs from pasting a repo into an LLM The usual failure mode of AI-generated docs is confidently describing call paths that don't exist. doc0 is built around not doing that: - It parses the repo with tree-sitter into a graph of functions, calls, and imports. A call only becomes an edge when the code proves it: same scope, an import, the same package, or a typed receiver. Anything it can't prove is stored as unresolved, not guessed. - Pages are written from that graph. A page about a flow gets real call paths from it. Every function and class a page mentions is checked against the graph, and a page with too many misses gets rewritten. - Quoted code is copied from the cited lines and linked to the commit the page was written from. - On push, only the pages your change touches get rewritten. I've been working on this for a while and I'm looking for honest feedback. Here you can find the generated wikis: doc0.dev/explore I'd love to hear your thoughts! Thanks!   submitted by   /u/Apart-Employment-592 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/10/12 18:24:52