llm-wiki
Build and maintain a structured LLM-generated wiki for any codebase. Use when the user asks to analyze/understand/document a codebase, build a code wiki, create project documentation from source, or update an existing .llm-wiki. Triggers on phrases like "build wiki", "analyze this codebase", "document this project", "update wiki", "llm-wiki", or when entering an unfamiliar project that has no .llm-wiki yet.
npx skills add staruhub/ClaudeSkills --skill llm-wiki --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# LLM Wiki for Codebases Build a persistent, interlinked markdown wiki that captures the architecture, modules, patterns, and APIs of a codebase. The wiki lives in `.llm-wiki/` at the project root. Humans curate and direct; the LLM handles all bookkeeping. Based on [Andrej Karpathy's LLM Wiki pattern](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f): raw sources are "compiled" into a structured wiki that compounds over time. ## Mode Detection Determine the mode based on current state: - **No `.llm-wiki/` directory exists** -> Full Build mode - **`.llm-wiki/` exists** -> Update mode (diff and refresh) ## Full Build Workflow ### Phase 1: Reconnaissance 1. Read top-level files: README, package.json/Cargo.toml/go.mod/pyproject.toml/build.gradle etc. 2. Run `find` or Glob to map the directory tree (ignore node_modules, .git, vendor, dist, build, __pycache__, .venv) 3. Identify: language(s), framework(s), build system, entry point(s), test framework 4. Count files per directory to gauge module boundaries 5. Read CLAUDE.md / AGENTS.md / .cursor/rules if present - they contain valuable architectural context Record findings in `.llm-wiki/_schema.md` (see references/wiki-sc
- Mode Detection
- Full Build Workflow
- Phase 1: Reconnaissance
- Phase 2: Skeleton
- Phase 3: Core Articles
- Phase 4: Index and Cross-link
- Phase 5: Lint
- Update Workflow
- Writing Guidelines
- Agent Coordination
- Gitignore
- Key Principles (from Karpathy)
What does the llm-wiki skill do?
Build and maintain a structured LLM-generated wiki for any codebase. Use when the user asks to analyze/understand/document a codebase, build a code wiki, create project documentation from source, or update an existing .llm-wiki. Triggers on phrases like "build wiki", "analyze this codebase", "document this project", "update wiki", "llm-wiki", or when entering an unfamiliar project that has no .llm-wiki yet.
How do I install it?
Run `npx skills add staruhub/ClaudeSkills --skill llm-wiki --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From staruhub/ClaudeSkills, a repository with 659 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.