wiki-ingest

# Ingest > **In the dev-loop plugin.** The wiki lives at the plugin root. When you run this > skill by hand for reference, read paths (`INDEX.md`, `wiki/`, `templates/`, > `AGENTS.md`) against **`${CLAUDE_PLUGIN_ROOT}/`**. When this skill is driven by > **`knowledge-flush`** to open a PR, that skill first prepares a **writable git > checkout of the dev-loop repo** and passes you its path as `<wiki_root>` — do all > reading and writing there (never edit the installed plugin dir, which is > read-only and untracked). `knowledge-flush` handles the branch/commit/PR after > you finish; your job is only the routed, sourced edit + plumbing update. Input: one unit of knowledge. Either a source (doc, article, post-mortem, benchmark) or a distilled lesson ("we hit X; doing Y fixed it because Z"). ## Steps 1. **Extract the case.** State the knowledge as: *trigger situation → directive → why → evidence*. If you cannot fill "trigger situation" precisely, stop: ask the contributor what situation makes this advice apply. Knowledge without a trigger cannot be routed and pollutes context. 2. **Convert prohibitions.** If the input arrives as "never do X" / "avoid X", rewrite it as the replacement action: "when <situation that tempts X>, do Y". Keep the prohibition only as an `Instead of` row paired with Y. 3. **Route.** Match the case to a domain via `INDEX.md`, then to a category via the domain `index.md`. If no category fits, create one (update the domain index) — b...