claude-skills/docs/commands/wiki-query.md
Claude 82c5aea9f0
Merge origin/dev: reconcile docs redesign with upstream skill changes
- Resolve conflicts: keep redesigned skills index, take dev's cs-aeo link
  fix, union of DOMAIN_SEO_CONTEXT entries in generate-docs.py
- Regenerate catalog on the merged tree (dev's agent/command description
  updates, removed ai-seo/release-manager/command-guide, restructured
  universal-scraping-architect)
- Update counters to post-merge truth from scripts/derive_counters.py:
  345 skills, 78 plugins (14 bundles + 64 standalone), 570+ Python tools
- Add redirects for upstream-removed pages (ai-seo -> aeo,
  release-manager -> changelog-generator, command-guide -> engineering index)
- Add compliance-os bundle to bundle tables; rebuild 78-plugin table from
  marketplace.json
- Teach the generator to rewrite repo-root-relative source links to GitHub
  URLs — mkdocs build --strict now passes with zero warnings

https://claude.ai/code/session_015bYZ97nV4oRb3LbxCRFVcP
2026-06-11 15:52:42 +00:00

67 lines
2.8 KiB
Markdown

---
title: "/wiki-query — Slash Command for AI Coding Agents"
description: "Query the LLM Wiki — reads index.md first, drills into 3-10 relevant pages, synthesizes an answer with inline [[wikilink]] citations, and offers to. Slash command for Claude Code, Codex CLI, Gemini CLI."
---
# /wiki-query
<div class="page-meta" markdown>
<span class="meta-badge">:material-console: Slash Command</span>
<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/commands/wiki-query.md">Source</a></span>
</div>
<!-- canonical copy: engineering/llm-wiki/commands/wiki-query.md — keep in sync (root copy uses repo-root-relative script paths) -->
# /wiki-query
Ask the wiki a question. The librarian reads `index.md` first, picks relevant pages across categories, synthesizes an answer with citations, and offers to file the answer back into the wiki so your explorations compound.
## Usage
```
/wiki-query "<your question>"
/wiki-query "what does the wiki say about sparse autoencoders?"
/wiki-query "compare monosemanticity and polysemanticity across my sources"
/wiki-query "which sources disagree on scaling laws?"
/wiki-query "give me a comparison table of SAE vs linear probing"
```
## What happens
1. **Index-first read** — reads `wiki/index.md` to find relevant pages
2. **Drill-in** — reads 3-10 pages in full (synthesis + concepts + sources + entities)
3. **Follow links** — opportunistically follows wikilinks between pages
4. **Fallback search** — if the index isn't enough, runs `engineering/llm-wiki/skills/llm-wiki/scripts/wiki_search.py` (BM25)
5. **Synthesize** — composes a direct answer + supporting detail + inline `[[sources/xxx]]` citations + "Related pages" section
6. **Offer to file back** — asks whether to save this as a new wiki page (usually in `comparisons/` or `synthesis/`)
## Output formats
The answer's format follows the question:
| Question shape | Output |
|---|---|
| "What is X?" | Markdown explanation with citations |
| "A vs B" | Comparison table |
| "Give me a slide deck on X" | Markdown synthesis → `/wiki-marp` to render |
| "Chart the trend in X" | Python script + saved chart in `wiki/assets/charts/` |
## Sub-agent
This command dispatches the `wiki-librarian` sub-agent. See `agents/wiki-librarian.md`.
## Scripts
- `engineering/llm-wiki/skills/llm-wiki/scripts/wiki_search.py` — BM25 fallback search
- `engineering/llm-wiki/skills/llm-wiki/scripts/append_log.py` — log filed answers
## Rules
- **Read the index first.** No grep-everything.
- **Every claim cites a page** with a `[[wikilink]]`.
- **Offer to file the answer back** — but only for substantive answers worth keeping.
## Skill Reference
→ `engineering/llm-wiki/skills/llm-wiki/SKILL.md`
→ `engineering/llm-wiki/skills/llm-wiki/references/query-workflow.md`