research-codebase

Documents the existing codebase via parallel read-only sub-agents and writes findings to flow/research/.

1|1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/corticalstack/flow --skill research-codebase-corticalstack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research-codebase
Source: https://github.com/corticalstack/flow/tree/main/.claude/skills/research-codebase
Command: npx skills add https://github.com/corticalstack/flow --skill research-codebase-corticalstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding a large or unfamiliar codebase requires hours of manual file reading, and ad-hoc exploration often loses context or produces undocumented findings. This Skill automates structured codebase research by spawning parallel read-only sub-agents and producing a durable, permalinked research document. ## Core Features & Use Cases - Parallel Sub-Agent Research: Spawns locator, analyzer, and pattern-finder agents concurrently to map where components live and how they work. - Structured Research Documents: Writes findings to flow/research/ with YAML frontmatter, git metadata, and clickable per-line repository permalinks. - Tracker Integration: Fetches work items from GitHub Issues or Azure DevOps and transitions their state as research progresses. - Use Case: A developer joining a project asks how authentication flows through the system; the Skill documents the current implementation with exact file and line references, without proposing changes. ## Quick Start Invoke /research-codebase and provide a research question or tracker issue URL to generate a documented map of the relevant codebase areas.

Frequently Asked Questions about research-codebase

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

FAQPage Schema
How do I research an unfamiliar codebase with AI agents?▼

Invoke the research-codebase command with a question or issue URL. It spawns parallel locator and analyzer sub-agents to map where components live and how they work, then synthesizes findings into a research document under flow/research/.

How to document existing code without getting refactoring suggestions?▼

This Skill enforces a strict documentarian role: all sub-agents describe what exists, where it lives, and how components interact, explicitly prohibiting critiques, recommendations, or root-cause analysis unless the user asks.

Does codebase research work with GitHub Issues or Azure DevOps?▼

Yes. When given a tracker URL or work-item id, it fetches the item via the tracker CLI, transitions its state to research-in-progress, and includes the work-item id in the research document filename.

What output format does the codebase research produce?▼

It writes a Markdown file to flow/research/ with YAML frontmatter (date, git commit, branch, tags, status), a summary, detailed findings, code references with clickable per-line permalinks, and historical context from prior flow documents.

Can I ask follow-up questions after the initial research?▼

Yes. Follow-up questions append a new timestamped section to the same research document, update the last_updated frontmatter fields, and may spawn additional sub-agents for further investigation.