code-researcher

Document codebase architecture and data flows with file:line references.

454|45|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/galz10/pickle-rick-extension --skill code-researcher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-researcher
Source: https://github.com/galz10/pickle-rick-extension/tree/main/skills/code-researcher
Command: npx skills add https://github.com/galz10/pickle-rick-extension --skill code-researcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of understanding and documenting a complex codebase. It guides you to produce a comprehensive, evidence-backed map of how components interact, where data flows, and where key patterns and dependencies reside.

Core Features & Use Cases

  • Document codebase structure and ownership
  • Trace data flows and identify inter-component communication
  • Map dependencies and critical paths
  • Produce an evidence-backed research report with file:line references

Quick Start

Document the current repository by generating a research report detailing architecture, data flows, and file-level references, and save it to the active session ticket folder.

Frequently Asked Questions about code-researcher

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

FAQPage Schema
How do I map an existing codebase and trace data flows across modules?

Mapping a codebase involves reading source files to identify key components and tracing data flows to produce an evidence-backed research report with file:line references detailing module interactions and dependencies.

What is the best way to document legacy code architecture with evidence?

Documenting legacy code requires analyzing source files to identify structural patterns and dependencies, generating an evidence-backed research report that maps architecture and inter-component communication with precise file:line references.

Can I generate a research report that traces inter-component communication in my repository?

Yes, you can generate a research report that traces inter-component communication and data flows by reading your repository's source files and mapping the interactions with structured file:line references.

How do I identify critical paths and dependencies across a complex codebase?

To identify critical paths and dependencies across a complex codebase, read the source files to map module interactions and trace data flows, then compile the findings into an evidence-backed research report with file:line references.

Does documenting codebase structure require specific environment setup or dependencies?

Documenting codebase structure requires access to readable source files within the active repository, and the resulting research report detailing architecture and data flows is saved directly to the active session ticket folder.