By psprowls
Build and maintain a persistent, cross-referenced markdown wiki alongside any source-code project — single packages, monorepos, or hybrid shapes. Adapts to the repo's folder structure: classifies top-level dirs as apps, packages, domains, or docs containers, and pins the layout in CLAUDE.md/AGENTS.md.
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 /code-ingest <path-to-source>
Bootstrap a fresh Code Wiki alongside a source code repo — three-layer structure, schema files, starter templates. Top-level wiki directory name is configurable (default llm-wiki); inner Obsidian vault dir defaults to <repo-name>-vault. Usage /code-init --wiki <path> --repo <path> --topic "<topic>" [--tool all|claude-code|codex|cursor|antigravity] [--vault-name <name>]
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). Outputs a markdown report with suggested actions. Usage /code-lint [--repo <path>] [--stale-days N]
Show recent entries from the Code Wiki log (<vault>/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 /code-query "<question>"
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 /code-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 /code-scan.
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 /code-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.
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, and docs containers and pins the layout in CLAUDE.md/AGENTS.md. Triggers include "wiki this repo", "document this codebase", "llm-code-wiki", "ingest this spec/PR/article into the wiki", or whenever the user wants a compounding, cross-referenced knowledge base alongside source code.
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A self-contained Claude Code plugin that lets the assistant build and maintain a persistent, cross-referenced markdown wiki alongside a source code repository — single packages, monorepos, or hybrid shapes.
llm-code-wiki detects the repo's top-level structure (single package, workspace-style monorepo, or hybrid) and adapts the vault layout to match. The chosen layout is pinned to <wiki>/CLAUDE.md and <wiki>/AGENTS.md so the LLM always knows what containers exist and where new pages belong.
The wiki has a fixed two-layer shape inside a configurable top-level dir (default llm-wiki/):
<wiki>/raw/ — immutable ingested sources<wiki>/<vault>/ — the LLM-curated Obsidian vault. <vault> defaults to <repo-name>-vault/ (e.g. mono-repo-vault/); override with --vault-name.This plugin is the successor to mono-wiki, which targeted monorepos exclusively. llm-code-wiki generalizes the same pattern to any repo shape.
plugins/llm-code-wiki/
├── .claude-plugin/
│ └── plugin.json
├── skills/
│ ├── llm-code-wiki/ # the maintainer skill (SKILL.md + scripts/ + references/ + assets/)
│ └── obsidian-markdown/ # Obsidian Flavored Markdown reference — invoked by agents when creating/editing/verifying vault pages
├── agents/ # ingestor, librarian, linter, scanner
└── commands/ # init, scan, ingest, query, lint, log
Add the plugin directory to your Claude Code settings (project-scoped under .claude/settings.json, or user-scoped under ~/.claude/settings.json):
{
"pluginDirectories": [
"/absolute/path/to/my-repo/plugins/llm-code-wiki"
]
}
Restart Claude Code (or run /reload-plugins if available). If the exact settings key has changed in your version of Claude Code, check the current plugin docs — what matters is that the absolute path to this plugin directory is registered. After install:
llm-code-wiki (same trigger description as before)./llm-code-wiki:init, /llm-code-wiki:scan, /llm-code-wiki:ingest, /llm-code-wiki:query, /llm-code-wiki:lint, /llm-code-wiki:log.llm-code-wiki:ingestor, llm-code-wiki:librarian, llm-code-wiki:linter, llm-code-wiki:scanner.All references to bundled python scripts use ${CLAUDE_PLUGIN_ROOT}, which Claude Code substitutes at load time with the absolute path to this plugin directory. That means the plugin can be installed from any path — no edits required.
Example (from inside an agent or command):
python ${CLAUDE_PLUGIN_ROOT}/skills/llm-code-wiki/scripts/lint_wiki.py --wiki . --repo <repo> --json
The scripts are pure-stdlib python; there is no install step.
.claude/While testing, the original assets remain in .claude/skills/llm-code-wiki/, .claude/agents/code-*, and .claude/commands/code-*. Once the plugin install is verified, those originals can be removed.
npx claudepluginhub psprowls/llm-code-wikiBuild and maintain a persistent, cross-referenced markdown wiki alongside any source-code project — single packages, monorepos, or hybrid shapes. Adapts to the repo's folder structure: classifies top-level dirs as apps, packages, domains, or docs containers, and pins the layout in CLAUDE.md/AGENTS.md. This is the Claude Code host path; graph-wiki-agent is the parallel Bedrock CLI companion over the same vault-io surface.
psprowlsClaude + Obsidian knowledge companion. Sets up a persistent, compounding wiki vault (Karpathy's LLM Wiki pattern). v1.7 "Compound Vault" + v1.8 methodology modes close 5 of 5 priority gaps from the May 2026 compass artifact. Ships: substrate alignment with kepano/obsidian-skills, default Obsidian CLI transport, hybrid retrieval (contextual prefix + BM25 + cosine rerank per Anthropic's Sept 2024 research), per-file advisory locking for multi-writer safety, pre-commit verifier agent, AND methodology modes (LYT / PARA / Zettelkasten / Generic) for first-class organizational support no other Claude+Obsidian competitor offers. v1.7.x audit closure: every BLOCKER + HIGH + MEDIUM + LOW finding from the v1.7.0 audit is CLOSED or DEFERRED-with-rationale. Optional DragonScale Memory extension (log folds, deterministic addresses, semantic tiling lint, boundary-first autoresearch).
AgriciDanielMake your AI agent code with your project's architecture, rules, and decisions.
archcore-aiComplete AI coding workflow system. Self-correcting memory + persistent FTS5-indexed research wikis + auto-research loop + multi-LLM council on a single SQLite store. 33 skills, 8 agents, 22 commands, 37 hook scripts across 24 events. Cross-agent via SkillKit.
rohitg00Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
upstashBuild and maintain an LLM-curated personal knowledge base in your project — Andrej Karpathy's LLM Wiki pattern, designed to scale to thousands of pages without becoming a context bottleneck. Now with an optional compiled graph layer for typed, provenance-backed relationships.
praneybehlAI-powered wiki generator for code repositories. Generates comprehensive, Mermaid-rich documentation with dark-mode VitePress sites, onboarding guides, deep research, and source citations. Inspired by OpenDeepWiki and deepwiki-open.
microsoft