prp-codebase-question

Answers codebase questions by spawning parallel research agents and generating evidence-based documentation.

2.2k|608|Updated Jun 21, 2025
One-click install
npx skills add https://github.com/Wirasm/PRPs-agentic-eng --skill prp-codebase-question
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prp-codebase-question
Source: https://github.com/Wirasm/PRPs-agentic-eng/tree/main/plugins/prp-core/skills/prp-codebase-question
Command: npx skills add https://github.com/Wirasm/PRPs-agentic-eng --skill prp-codebase-question

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understanding how an unfamiliar or large codebase works requires hours of manual searching, reading, and tracing. This Skill automates that investigation by dispatching parallel specialized agents to locate code, trace data flows, and document findings with precise file:line references.

Core Features & Use Cases

  • Parallel Agent Research: Decomposes a question into 2-5 research areas and assigns them to codebase-explorer, codebase-analyst, or web-researcher agents running in parallel.
  • Evidence-Based Documentation: Produces a structured research document where every claim is backed by a file:line reference, with optional GitHub permalinks.
  • Follow-Up and Web Research: Supports --follow-up to append new findings to existing research files and --web to include external documentation.
  • Use Case: Ask "how does authentication work" and receive a dated research document in your PRP store describing the actual implementation, architecture, and code references—without opinions or refactoring suggestions.

Quick Start

Ask the agent to research how authentication works in this codebase using /prp-codebase-question and save the findings as a research document.

Frequently Asked Questions about prp-codebase-question

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

FAQPage Schema
How do I research how a codebase works with AI agents?

Invoke /prp-codebase-question with your question, and it decomposes the query into research areas handled by parallel explorer and analyst agents. The findings are synthesized into a research document with file:line references for every claim.

How to trace data flow through an unfamiliar codebase?

Use a 'how does' or 'trace' style question, which routes the work to the codebase-analyst agent. It traces data flow, integration points, and contracts between components, documenting what exists with precise file:line references.

Can codebase research include external documentation?

Yes, pass the --web flag to add a web-researcher agent that fetches external documentation, API references, and best practices. External findings supplement the live codebase, which remains the primary source of truth.

Does the codebase research skill suggest code improvements?

No, it operates strictly as a documentarian. It describes what exists, where it lives, and how components interact, and explicitly avoids suggestions, critiques, root cause analysis, or refactoring recommendations.

Where are the generated codebase research documents saved?

Research files are saved as dated markdown documents under the research directory of your project's PRP store, resolved via git metadata. With --follow-up, new findings are appended to an existing research file instead.