// Run the complete llmwiki pipeline from scratch — init, sync, graph, build, lint, and serve. Use when the user says "run everything", "full pipeline", "wiki-all", or wants to rebuild the entire wiki from session history.
| name | wiki-all |
| description | Run the complete llmwiki pipeline from scratch — init, sync, graph, build, lint, and serve. Use when the user says "run everything", "full pipeline", "wiki-all", or wants to rebuild the entire wiki from session history. |
Runs the complete llmwiki pipeline in the correct sequence:
raw/, wiki/, site/ directories.jsonl sessions to markdownwiki/ markdown into site/ HTMLRun each step in order. Report the result of each before proceeding to the next.
python3 -m llmwiki init
Report what was created or confirmed.
python3 -m llmwiki sync --no-auto-build --no-auto-lint
Report: how many sessions converted, how many unchanged, any errors.
If new sessions were converted, follow the Ingest Workflow from CLAUDE.md for each new file (create/update entity + concept pages, cross-link, update index).
python3 -m llmwiki graph
Report: node count, edge count, community count, top 5 connected nodes.
Ask the user: "Export graph to Obsidian vault?" If yes:
python3 -c "
from llmwiki.graphify_bridge import export_to_obsidian
from pathlib import Path
export_to_obsidian(Path.home() / 'Documents/Obsidian Vault/Temp/Graph')
"
python3 -m llmwiki build
Report: HTML file count, total size, export formats written.
python3 -m llmwiki lint
Report: total issues by severity (errors, warnings, info). Highlight any errors that need immediate attention.
Ask the user: "Start the local server?" If yes:
python3 -m llmwiki serve --open
Report the URL: http://127.0.0.1:8765
Report a summary table:
| Step | Result |
|---|---|
| init | N dirs, M seed files |
| sync | N converted, M unchanged |
| graph | N nodes, M edges, K communities |
| build | N HTML files, M MB |
| lint | N issues (E errors, W warnings) |
| serve | http://127.0.0.1:8765 |
Ingest one source document (or a folder of them) into the llmwiki. Use when the user drops a new markdown file, PDF, or URL into the wiki and asks you to process it. The user will typically say "ingest this", "add this to the wiki", "process this file into the wiki", or point at a file under `raw/`.
Answer a question by querying the user's llmwiki. Use when the user asks about their own past work — "what did I decide about X", "what have I been working on", "how did I solve Y", "what's my preferred approach to Z", or any question that the wiki (built from their session history) might answer. Always read the wiki first before falling back to external search.
Sync Claude Code session transcripts into the user's llmwiki and ingest them into the wiki. Use when the user says "sync the wiki", "update llmwiki", "ingest recent sessions", "refresh the knowledge base", or asks a knowledge question that would benefit from up-to-date sessions. Also use when the user explicitly asks to refresh or rebuild the LLM wiki from their agent history.
Maintain an llmwiki-style open-source project across the full framework pipeline. Use when the user says "maintain the project", "check my tasks", "update progress", "run phase gate", "do a monthly verify", "lint my wiki", "check stale entries", or invokes any form of ongoing project-keeping chore. Reads _progress.md, tasks.md, docs/roadmap.md, and .github issues to figure out what's next and what's drifted.
Extract reusable patterns from recent sessions, propose framework improvements, and (with approval) update the framework docs. This is the dogfooding meta-loop — the project learns from its own usage. Use when the user says "learn from this", "what did we learn", "extract lessons", "update the framework", "add this to steering rules", or after completing any substantial feature or debugging session.