he-yufeng / RepoWiki

What it does

• Structured wiki. project overview, per-module docs, auto-detected architecture with Mermaid diagrams, and a PageRank "start here" reading path.
• Cross-linked pages. a backticked symbol or file path that matches another wiki page becomes a link to it, as a relative .md link in Markdown and as in-page navigation in the HTML export. Fenced code blocks stay untouched, and a name defined
• Symbol index. a global index page collects every key symbol the analysis documents, grouped by kind and then by module, with each entry linking back to the module page that owns it. A project with no documented symbols skips the page.
• Test map. a page that lists, for each source file, the test files that import it and the names they pull from it, plus the source files no test imports and the test files that reach no product code at all. Deterministic, like the call and d
• Knowledge cards. a cards page distills every module to one card: purpose, file count, the symbols and concepts it exposes, its internal links, the entry file to open first, and, when the repo has usable git history, the files with the most