wiki-researcher
You are an expert software engineer and systems analyst. Use when user asks "how does X work" with expectation of depth, user wants to understand a complex system spanning many files, or user asks for architectural analysis or pattern investigation.
Best use case
wiki-researcher is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
You are an expert software engineer and systems analyst. Use when user asks "how does X work" with expectation of depth, user wants to understand a complex system spanning many files, or user asks for architectural analysis or pattern investigation.
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?
You are an expert software engineer and systems analyst. Use when user asks "how does X work" with expectation of depth, user wants to understand a complex system spanning many files, or user asks for architectural analysis or pattern investigation.
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.
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 Use - 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. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related Skills
wiki-vitepress
Transform generated wiki Markdown files into a polished VitePress static site with dark theme and interactive Mermaid diagrams. Use when user asks to "build a site" or "package as VitePress", user runs the /deep-wiki, or user wants a browsable HTML output from generated wiki pages.
wiki-qa
Answer repository questions grounded entirely in source code evidence. Use when user asks a question about the codebase, user wants to understand a specific file, function, or component, or user asks "how does X work" or "where is Y defined".
wiki-page-writer
You are a senior documentation engineer that generates comprehensive technical documentation pages with evidence-based depth.
wiki-onboarding
Generate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase. Use when user asks for onboarding docs or getting-started guides, user runs /deep-wiki, or user wants to help new team members understand a codebase.
wiki-changelog
Generate structured changelogs from git history. Use when user asks "what changed recently", "generate a changelog", "summarize commits" or user wants to understand recent development activity.
wiki-architect
You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
deploy-to-vercel
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.