doc-wiki

doc-wiki

60-second demo: media/demo.mp4 · 2-minute product overview: media/product-explainer.mp4 · reproducible benchmark: benchmark/

The LLM Wiki layer for enterprise coding agents.

Your coding agent — Claude Code, Codex, Antigravity, OpenCode, Gemini, Cursor, or Aider — reads an ecosystem-aware wiki of your code (single repo, monolith, or root-of-microservices in submodules) before it touches the diff. One command, /doc-wiki:atlas, documents the whole codebase: per-topic architecture pages, ER diagrams derived from your actual ORM models, a cross-service map generated automatically when it sees more than one service, and cited answers via /doc-wiki:query. Jira / Confluence / GitHub / GitLab / Notion / Linear / AWS / GCP and your DB schemas route in through one connector planner — configure credentials once.

_{Does the wiki make the agent fix more tickets fully autonomously? We built a hardened benchmark and measured: four configurations, 92 paired runs on OSS repos — no measured lift, and we publish that null in full at benchmark/RESULTS.md. What doc-wiki demonstrably gives you is the artifact: the map, the diagrams, the history, the cited answers — context you and your agent navigate together. The author's ~10%→~50% experience on a private 500k-LOC enterprise codebase is exactly that: one engineer's anecdote, in a regime (ecosystem-heavy enterprise code, human in the loop) the benchmark doesn't reach. Scales down too: a small single-repo project gets the same wiki, leaner.}

claude plugin install narailabs/doc-wiki
5-min walkthrough · reproducible benchmark · Apache-2.0 forever

doc-wiki is a tool you run inside your coding agent — Claude Code, Codex, Antigravity, OpenCode, Gemini, Cursor, and Aider all read the same wiki via their standard project-convention files (CLAUDE.md, AGENTS.md, GEMINI.md, etc. — see multi-platform wrappers). Seven /doc-wiki:* slash commands cover the full lifecycle: init (scaffold + onboard), atlas (full-codebase documentation in one pass), ingest, query, lint, edit, and stats. External services are reached through a single planner — gather() from narai-primitives — so you configure credentials once and every command can use them.

Why this exists

Claude Code is shockingly good on clean, small, well-documented codebases. On real-world enterprise codebases — eight years of accumulated patterns, a database schema that drifted from the ORM models three refactors ago, half the answers buried in old Jira tickets, decision rationale stuck in GitHub PR discussions from a year ago — it falls off a cliff. The model can't see what isn't in its context window, and dumping the whole repo is impossible (and useless even when it fits).

Andrej Karpathy named the LLM Wiki pattern in April 2026: a maintained, compounding artifact of distilled knowledge that an LLM reads instead of re-deriving everything from raw sources every time. doc-wiki applies that pattern to enterprise code — and extends it to ingest Jira, Confluence, GitHub, Notion, AWS, GCP, and your ORM/DB schemas, so the wiki carries the whole ecosystem your codebase actually depends on, not just the code.

The output is a structured wiki under docs/<app>-wiki/. Your coding agent reads it (via CLAUDE.md, AGENTS.md, GEMINI.md, or whichever convention your agent uses) before touching code. /doc-wiki:atlas documents an entire codebase in one phased pass; /doc-wiki:ingest keeps it current as the project evolves; /doc-wiki:query returns cited answers synthesised from wiki pages. Seven /doc-wiki:* slash commands cover the lifecycle; external services route through one planner — gather() from narai-primitives — so you configure credentials once and every command can use them. Everything runs inside your existing agent session. No SaaS, no daemon, no telemetry.