focused-fix
Deep-dive feature repair — systematically fix an entire feature/module across all its files and dependencies. Usage: /focused-fix <feature-path>
Query the LLM Wiki — reads index.md first, drills into 3-10 relevant pages, synthesizes an answer with inline [[wikilink]] citations, and offers to file the answer back as a new comparison or synthesis page. Usage /wiki-query "<question>
$ npx -y skills add alirezarezvani/claude-skills --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/wiki-queryContext preview
What this command does when you run it.
Query the LLM Wiki — reads index.md first, drills into 3-10 relevant pages, synthesizes an answer with inline [[wikilink]] citations, and offers to file the answer back as a new comparison or synthesis page. Usage /wiki-query "<question>
name: wiki-query 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 file the answer back as a new comparison or synthesis page. Usage /wiki-query "<question>"
<!-- canonical copy: engineering/llm-wiki/commands/wiki-query.md — keep in sync (root copy uses repo-root-relative script paths) -->
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.
/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"
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/`)
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/` |
This command dispatches the `wiki-librarian` sub-agent. See `agents/wiki-librarian.md`.
→ `engineering/llm-wiki/skills/llm-wiki/SKILL.md` → `engineering/llm-wiki/skills/llm-wiki/references/query-workflow.md`
388 production-ready Claude Code skills, plugins, and agent skills for 13 AI coding tools. The most comprehensive open-source library of Claude Code skills and agent plugins — also works with OpenAI Codex, Gemini CLI, Cursor, and 9 more coding agents.
Repo: alirezarezvani/claude-skills
Deep-dive feature repair — systematically fix an entire feature/module across all its files and dependencies. Usage: /focused-fix <feature-path>
Clean up merged branches locally and on remote, keeping only main, dev, and gh-pages.
Stage, commit, and push the current branch following git governance rules.
Comprehensive audit pipeline for skills, plugins, agents, and commands. Validates structure, quality, security, marketplace compliance, cross-platform…