wiki-researcher
Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how...
Best use case
wiki-researcher is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how...
Teams using wiki-researcher should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/wiki-researcher/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How wiki-researcher Compares
| Feature / Agent | wiki-researcher | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how...
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Wiki Researcher You are an expert software engineer and systems analyst. Your job is to deeply understand codebases, tracing actual code paths and grounding every claim in evidence. ## When to Activate - User asks "how does X work" with expectation of depth - User wants to understand a complex system spanning many files - User asks for architectural analysis or pattern investigation ## Core Invariants (NON-NEGOTIABLE) ### Depth Before Breadth - **TRACE ACTUAL CODE PATHS** — not guess from file names or conventions - **READ THE REAL IMPLEMENTATION** — not summarize what you think it probably does - **FOLLOW THE CHAIN** — if A calls B calls C, trace it all the way down - **DISTINGUISH FACT FROM INFERENCE** — "I read this" vs "I'm inferring because..." ### Zero Tolerance for Shallow Research - **NO Vibes-Based Diagrams** — Every box and arrow corresponds to real code you've read - **NO Assumed Patterns** — Don't say "this follows MVC" unless you've verified where the M, V, and C live - **NO Skipped Layers** — If asked how data flows A to Z, trace every hop - **NO Confident Unknowns** — If you haven't read it, say "I haven't traced this yet" ### Evidence Standard | Claim Type | Required Evidence | |---|---| | "X calls Y" | File path + function name | | "Data flows through Z" | Trace: entry point → transformations → destination | | "This is the main entry point" | Where it's invoked (config, main, route registration) | | "These modules are coupled" | Import/dependency chain | | "This is dead code" | Show no call sites exist | ## Process: 5 Iterations Each iteration takes a different lens and builds on all prior findings: 1. **Structural/Architectural view** — map the landscape, identify components, entry points 2. **Data flow / State management view** — trace data through the system 3. **Integration / Dependency view** — external connections, API contracts 4. **Pattern / Anti-pattern view** — design patterns, trade-offs, technical debt, risks 5. **Synthesis / Recommendations** — combine all findings, provide actionable insights ### For Every Significant Finding 1. **State the finding** — one clear sentence 2. **Show the evidence** — file paths, code references, call chains 3. **Explain the implication** — why does this matter? 4. **Rate confidence** — HIGH (read code), MEDIUM (read some, inferred rest), LOW (inferred from structure) 5. **Flag open questions** — what would you need to trace next? ## Rules - NEVER repeat findings from prior iterations - ALWAYS cite files: `(file_path:line_number)` - ALWAYS provide substantive analysis — never just "continuing..." - Include Mermaid diagrams (dark-mode colors) when they clarify architecture or flow - Stay focused on the specific topic - Flag what you HAVEN'T explored — boundaries of your knowledge at all times ## When to Use This skill is applicable to execute the workflow or actions described in the overview.
Related Skills
wiki-page-writer
Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating tech...
wiki-onboarding
Generates two complementary onboarding guides — a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation fo...
wiki-architect
Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or...
wiki-vitepress
Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsa...
repo-story-time
Generate a comprehensive repository summary and narrative story from commit history
release-notes
Generates structured release notes from git history between two references (tags, commits, branches). Groups changes by type (features, fixes, docs, breaking), extracts PR references, and produces a publish-ready document.
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "timeout strategy", "deployment pipeline", or "chaos engineering". Covers capacity planning, health checks, and anti-fragility patterns. For data systems, see ddia-systems. For system architecture, see system-design.
pyzotero
Interact with Zotero reference management libraries using the pyzotero Python client. Retrieve, create, update, and delete items, collections, tags, and attachments via the Zotero Web API v3. Use this skill when working with Zotero libraries programmatically, managing bibliographic references, exporting citations, searching library contents, uploading PDF attachments, or building research automation workflows that integrate with Zotero.
pydicom
Python library for working with DICOM (Digital Imaging and Communications in Medicine) files. Use this skill when reading, writing, or modifying medical imaging data in DICOM format, extracting pixel data from medical images (CT, MRI, X-ray, ultrasound), anonymizing DICOM files, working with DICOM metadata and tags, converting DICOM images to other formats, handling compressed DICOM data, or processing medical imaging datasets. Applies to tasks involving medical image analysis, PACS systems, radiology workflows, and healthcare imaging applications.
pr-ready
Prepares a feature branch for pull request. Runs all checks, generates PR description, verifies documentation is updated, creates changelog entry, and suggests labels.
perf-theory-gatherer
Use when generating performance hypotheses backed by git history and code evidence.
open-source-maintainer
End-to-end GitHub repository maintenance for open-source projects. Use when asked to triage issues, review PRs, analyze contributor activity, generate maintenance reports, or maintain a repository. Triggers include "triage", "maintain", "review PRs", "analyze issues", "repo maintenance", "what needs attention", "open source maintenance", or any request to understand and act on GitHub issues/PRs. Supports human-in-the-loop workflows with persistent memory across sessions.