RepoFold

Your codebase, explained. Always current.

7 followers

Your codebase, explained. Always current.

7 followers

Visit website

Knowledge base software

RepoFold turns a GitHub repo into a wiki you can trust: every claim cites the exact file and lines, validated against the parsed source. It updates itself on every push, and coding agents can query it over MCP. Free during beta.

Free

Launch tags:Developer Tools•GitHub•Tech

Launch Team / Built With

Viktor.comAn AI coworker that actually does the work

Promoted

Maker

📌

Hey Product Hunt, I built RepoFold because my own README lied to me. I came back to a project after six months and my setup instructions described env vars that no longer existed and a service I had deleted. Docs rot because updating them always loses from writing code. AI-generated docs seemed like the fix, until I checked the details: invented config options, an auth flow we never had. Wrong docs that look right are worse than no docs. So RepoFold has one hard rule: no sentence ships unless it can prove itself. Every claim in every generated page carries a citation to the exact file and lines, and that citation is validated against the actually parsed source before the page is published. Click any statement and you are looking at the code that backs it. Because the wiki is generated from the code, it keeps itself current: push to main and only the sections that actually changed get rewritten. There is a changelog showing how your documentation evolved with your commits. Unexpected favorite feature: the MCP server. Claude Code, Cursor or Codex can query the wiki ("where is rate limiting enforced?") and get answers with file and line citations instead of grepping the whole checkout. It is free during the beta (one repo, public or private, read-only access). I am here all day and I would genuinely love to hear where it gets your codebase wrong.

Report

2mo ago

Love that every claim cites the file and line range, that's exactly what was missing from the AI doc tools I tried. One thing I'd find useful is letting me mark certain folders or file patterns as off-limits so generated wiki pages never include things like vendored code or generated mocks. Would keep the docs focused on the parts that actually matter.

Report

1mo ago

Maker

@sercan254205 Thanks for the tips, i will write this point down to discuss maybe in feature patches :)

Report

1mo ago

Forum Threads

p/repofold

•

2mo ago

Would you trust documentation your team didn't write?

Maker here...

RepoFold generates a wiki from your GitHub repo, and the whole design revolves around one rule: no sentence ships unless it can cite the exact file and lines it came from, verified against the parsed source.

View all