Generate a documentation wiki from your codebase.
Point Wiki Pilot at a repo. It reads what's actually there and drafts a sectioned wiki — then records which source files every page was built from, so you can tell which pages have fallen behind the code.
Someone writes the page the week the feature ships. Then the feature keeps changing for two years.
Nothing on the page says whether it still matches the code.
Usually by whoever followed the instructions into a broken deploy, and then asked in Slack anyway.
Code moves faster than anyone writes it down.
An afternoon with a coding agent can touch more files than a team used to change in a sprint. Nobody decides to let a page go out of date — documentation drift happens between one merge and the next, and by the time anyone notices, the page has been wrong for a month.
Wiki Pilot makes that measurable instead of hoping. Each page names the paths it covers and the commit and release it was last checked against. Rewrite a service overnight and every page describing it flags itself on the next build — so reviewing what the agent changed is a list you work through, not an excavation.
From repo to published wiki, in four steps.
Pick a type
wikipilot init asks who the wiki is for: technical, user guide, or both (the default). Your answer decides which sections get drafted.
Investigate
A draft lands instantly from the README and manifest. Then an AI agent — Claude, OpenAI, or Gemini over the API, or Claude Code on your own plan — digs through the source and rewrites the pages from what the code actually does, following your wikipilot.md brief if you wrote one.
Build
One folder of static files. Host it wherever you already host things.
Resync
Edit the code and the pages built from those files start showing a "may be outdated" banner. The bundled Claude Code skill can then rewrite them against the current source.
Real wikis, generated from repos you know.
Each of these was generated from the project's public repository — drafted by the CLI, rewritten by an AI investigation of the source, and not hand-edited afterwards. Open one and poke around — the navigation, search, and diagrams are all standard output.
Express
The Node.js web framework. See the middleware stack and router traced from lib/, not paraphrased from the README.
Zod
TypeScript schema validation. What actually happens inside schema.parse(), diagrammed from the source.
Hono
The multi-runtime web framework. How one app object serves Cloudflare Workers, Deno, Bun, and Node.
hono.wikipilot.devIndependent demonstrations of Wiki Pilot output. Not affiliated with or endorsed by the Express, Zod, or Hono projects.
What you get in the box.
Freshness contract
Change a file the page depends on and the rendered page grows a banner at the top: may be outdated, verified at commit abc1234. The next person hears it from the wiki instead of from you.
An agent that reads the code
Add an API key and init goes past the README: an agent lists, greps, and traces its way through the repo, then rewrites the pages from what it found — snippets copied out of real files, diagrams that follow actual call paths, and an onboarding path for whoever joins the team next. Claude Opus 5.5 by default, or OpenAI, Gemini, or your own endpoint. No API credits but Claude Code installed? --engine claude-code runs the same pass on your plan.
A brief it follows
Drop a wikipilot.md at the repo root to say what the code can't: who reads the wiki, which journeys matter, what each section should hold. It can even replace the section list, so a product with customers and agencies gets a guide for each. Every route or number in the brief gets checked against the code before it reaches a page.
Pictures, in your colours
Name the sites it may load and the agent screenshots the pages it documents, using the Playwright your end-to-end tests already installed. It looks at each capture before embedding it. Signed-in and native-app screens come from images already in the repo. The built wiki takes your brand colours, fonts and logo from your own Tailwind or CSS, nudged where needed so links stay readable.
A skill that maintains it
init writes a Claude Code skill into your repo. Ask it to update the wiki and it re-reads the changed files, rewrites the affected prose, and re-stamps the pages it was sure about. The ones it wasn't sure about get flagged rather than guessed.
Static output, search included
Put the output folder in a bucket, a Pages project, or behind your VPN — there's no process to keep alive, and full-text search runs in the browser against a prebuilt index. The one optional exception is the ask-the-wiki assistant: a separate server, grounded in the wiki's own pages, that says so when something isn't documented instead of producing a confident guess.
Three fields in the frontmatter do all the work.
sources — glob patterns, as narrow as you can make them.
last_synced — a commit SHA. Diffing it against HEAD is the whole detection mechanism.
stale — a boolean anyone can set by hand when they know a page is wrong but can't fix it yet.
It's plain YAML in a Markdown file. Nothing stops you writing it by hand, and nothing breaks if you do.
The CLI is MIT licensed and stays that way.
Everything on this page works without an account, a key, or a subscription. The hosted tier is the only thing anyone pays for.
Start free. Upgrade when hosting gets old.
Try it on a repo you already know.
You'll know within five minutes whether the pages it drafts are worth keeping. That's the whole evaluation.
Something to add?
Bug, feature idea, or just a thought on how this could be better — tell us.
Or email [email protected] directly.