woz-knowledgelisted

# WozCode KnowledgeBase — inspect and customize The WozCode knowledge base has three layers, queried bottom-up: | Layer | Source | Sync? | |---|---|---| | **company** | org-wide chunks (cross-repo learned rules) | server (v2) | | **repo** | code files + PR history + distilled rules | local (v1) / server (v2) | | **personal** | your notes, suppressions, boosts | local (v1) / server (v2) | This skill is a thin wrapper around the `wozcode knowledge` CLI subcommand. It's the right tool when the user wants to: - See what's indexed (`status`) - Search the knowledge base semantically (`query`) - Add a personal note that the reviewer will surface in future runs (`note`) - Hide a chunk the reviewer keeps citing (`suppress`) - Boost the relevance of a chunk that should weigh more (`boost`) - Ingest a one-off file (`ingest`) - Refresh the repo knowledge base (`refresh`) - See your overlay history (`ops`) ## When to use TRIGGER on: - "woz knowledge", "knowledge base status", "what's in the knowledge base", "is the knowledge base built" - "search the knowledge base for ...", "query the knowledge base", "woz recall" (note: distinct from `/woz-recall` which searches past Claude Code sessions) - "add a knowledge-base note", "remember that X", "tell the knowledge base ..." - "suppress this", "stop the reviewer from citing X" - "boost this", "make X more relevant" - "ingest <file> into the knowledge base", drag-and-drop scenarios - "refresh the knowledge base", "rebuild the knowledge bas