wiki-researcher

Trace execution paths across codebase files with file:line citations.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/RemseyMailjard/superpowers --skill wiki-researcher-remseymailjard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-researcher
Source: https://github.com/RemseyMailjard/superpowers/tree/main/.github/skills/wiki-researcher
Command: npx skills add https://github.com/RemseyMailjard/superpowers --skill wiki-researcher-remseymailjard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deeply analyzes codebases to trace actual execution paths and ground conclusions in verifiable evidence.

Core Features & Use Cases

  • Iterative, multi-file investigations spanning components and modules
  • Evidence-backed conclusions with file:line citations to support claims
  • Architectural pattern analysis and system-wide traceability across the codebase

Quick Start

Provide a thorough, evidence-backed analysis by tracing actual code paths and citing concrete file paths.

Frequently Asked Questions about wiki-researcher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace execution paths across multiple files in a codebase?

Trace execution paths across multiple files by iteratively investigating components and modules, grounding conclusions with verifiable file:line citations to support end-to-end traceability claims.

What is the best way to analyze architectural patterns with evidence?

Analyze architectural patterns by investigating system-wide traceability across the codebase, requiring precise file-path citations and source-backed conclusions to support claims about data flows and integration points.

How do I investigate data flows and integration points spanning multiple modules?

Investigate data flows and integration points by tracing actual execution paths across modules, providing evidence-backed conclusions with precise file-path citations for verifiable multi-file analysis.

Can I use this for codebase research on topics spanning multiple modules?

Use this for codebase research on topics spanning multiple files or modules, including architectural patterns, data flows, and integration points, requiring end-to-end traceability with verifiable, source-backed conclusions.

Why does my codebase analysis lack traceability for architectural patterns?

Codebase analysis lacks traceability when conclusions are not grounded in evidence, requiring iterative multi-file investigations that cite concrete file paths and trace actual execution paths to support claims.

Does wiki-researcher work for multi-file investigations requiring source-backed conclusions?

Wiki-researcher works for multi-file investigations by tracing actual execution paths and grounding conclusions in verifiable evidence, providing precise file-path citations to support claims across components and modules.