graph-wiki

Bootstrap a fresh Code Wiki in the resolved graph-wiki workspace — schema files and starter templates. Wiki is created at <workspace>/wiki/. Usage /graph-wiki:bootstrap --topic "<topic>" [--tool all|claude-code|codex|cursor|antigravity]

Ingest a source file from raw/ into the Code Wiki — read, discuss, write summary, update package/domain/concept pages, propose ADRs if decisions are captured, flag contradictions with code, update index, append to log. Usage /graph-wiki:ingest <path-to-source>

Run a health check on the Code Wiki — mechanical (orphans, broken links, stale pages, missing frontmatter, duplicates, log gap), semantic (contradictions, cross-reference gaps, stale claims, roadmap staleness, ADR chain), and code-drift (packages on disk vs. in vault, exports mismatch). Workspace and repo discovered automatically. Outputs a markdown report grouped under "## Wiki lint" header. Usage /graph-wiki:lint [--stale-days N]

Show recent entries from the Code Wiki log (<workspace>/wiki/log.md). Uses the standardized

Query the Code Wiki — reads index.md first, drills into 3-10 relevant pages (packages, domains, concepts, architecture, ADRs, sources), synthesizes answer with inline [[wikilinks]] and `code-paths:line`, and offers to file the answer back. Usage /graph-wiki:query "<question>"

Dispatched sub-agent that ingests a source file from raw/ into the Code Wiki. Reads the source, proposes TL;DR and key claims, identifies which package/domain/concept pages will be touched, flags contradictions with wiki or code, proposes ADRs when decisions are captured, and — after user confirmation — writes the source summary, updates 5-15 cross-referenced pages, regenerates the index, and logs the ingest. Spawn when the user says "ingest this", "add this spec/article/PR to the wiki", or runs /graph-wiki:ingest.

Dispatched sub-agent that answers queries against a Code Wiki. Reads index.md first, drills into 3-10 relevant pages across categories (architecture, packages, domains, concepts, ADRs, sources, issues, roadmap), synthesizes an answer with inline [[wikilink]] and `code-path:line` citations, and offers to file the answer back as a new concept/architecture/comparison page. Spawn when the user asks a substantive question about the monorepo the wiki might answer.

Dispatched sub-agent that runs a health check on a Code Wiki. Mechanical checks via scripts (orphans, broken links, stale pages, missing frontmatter, duplicate titles, log gaps, CODE DRIFT), semantic checks (contradictions vault↔vault and vault↔code, stale claims, concept gaps, issue/ticket sync, roadmap staleness, ADR chain health, cross-reference gaps, index drift), and produces a markdown report with suggested actions. Spawn weekly, after batch ingests, after /graph-wiki:scan, or when the user says "lint the wiki" / "check the wiki".

Dispatched sub-agent that walks the monorepo to detect workspace packages (from package.json, pyproject.toml, Cargo.toml, go.mod), diffs against the vault's package/app/domain folders, and proposes/creates/updates stub package pages. Flags renames and deletions for user confirmation. Spawn when the user says "scan the monorepo", "update package pages", "catch the wiki up to the code", or runs /graph-wiki:scan.

Use when building or maintaining a persistent wiki alongside any source-code project — single packages, monorepos, or hybrid shapes. Adapts to the repo's folder structure: detects app, package, domain, package-family, and docs containers and pins the layout in CLAUDE.md/AGENTS.md. Triggers include "wiki this repo", "document this codebase", "graph-wiki", "ingest this spec/PR/article into the wiki", or whenever the user wants a compounding, cross-referenced knowledge base alongside source code.