Skip to main content
After the first compile, you rarely need to recompile everything. The wiki compiler tracks which source files have changed and only reprocesses the topics that need updating. INDEX.md is always regenerated.

​
Compile commands

Incremental is the default and the fastest option for day-to-day use. Use --full when you’ve made significant changes to schema.md or article_sections and want every article to reflect the updated structure. Use --topic to quickly refresh one topic without touching the rest of the wiki.
After any compile run, use /wiki-lint to check wiki health. Lint catches stale articles, orphan pages, missing cross-references, and contradictions — it’s the fastest way to confirm your wiki is in good shape.

​
Adding a single file interactively

When you want to add one new source file and stay involved in how it gets integrated, use /wiki-ingest:
The workflow is interactive:
  1. Claude reads the file and presents 3–5 key takeaways.
  2. You tell Claude what to emphasize or de-emphasize.
  3. Claude shows you which existing topics the file touches and asks for confirmation.
  4. Claude updates each affected topic article and regenerates INDEX.md.
A single source can touch multiple topics — /wiki-ingest handles the cross-referencing automatically. Use /wiki-compile for batch processing and /wiki-ingest when you want to guide what gets captured.

​
Automated daily compilation

Use Claude Code’s /schedule command to set up automatic compilation on a recurring schedule. A daily incremental compile keeps your wiki current without any manual steps.

​
Updating the plugin

To pull the latest version of the plugin from GitHub:
This shows you what changed before applying the update. Restart Claude Code after running /wiki-upgrade so the new commands and hooks load correctly. If /wiki-upgrade is not available (you’re on an older version), update manually:
Then restart Claude Code.