A wiki that keeps up with main
Turn on the wiki for a repository and inline writes its documentation from the code: an overview, the architecture, a page per module, the key flows, where-to-change guides and a glossary. It rebuilds on every push to the default branch, and it checks every merged pull request against the docs you already have.
Generated from the code,
rebuilt on every push
Turn on a generated wiki for a repository: an overview, the architecture, a page per module, the key flows and a glossary, rebuilt on every push to the default branch. When a merged pull request makes the repository's own docs wrong, inline quotes the stale sentence and offers a docs fix.
How it works
Only the pages
whose code changed
A build regenerates only the pages whose code changed, with every decision on the record. A page whose inputs did not change is left alone and says so. Every build and every skipped push is listed, so you can tell when a page was last written and why.
Docs drift,
caught at merge
Every pull request merged into the default branch is checked against the docs that mention what it changed. When a merge makes a sentence wrong, inline quotes it and offers a fix. Someone who disagrees records why the docs are still right, and the note stays with the finding.
Readable by your
coding agents
The wiki is readable by coding agents over MCP, so an agent planning a change reads the same architecture notes a new engineer would. From the terminal, inline wiki search finds a page. Both read the same pages the portal shows.
Included
Related
Learnings
Teach inline a rule from a pull request. It drafts rules from what your team dismisses and fixes, and retires the ones the evidence stops backing.
Read moreCode graph
A commit-anchored graph of symbols, calls and imports that the reviewer walks instead of grepping, following the real dependency closure of a change.
Read moreCoding agents
An MCP server any coding agent can call for a review before the pull request exists, and visual plans a person signs off before the agent writes code.
Read more
Put it on one repository
Connect GitHub or GitLab, enable a repo, and the next pull request opened gets a review.