# Research Codebase

Document and explain the codebase as-is using parallel sub-agents.

- Repository: https://github.com/modiqo/skillspec (699 stars)
- Category: AI and agents
- License: Apache-2.0
- Last updated: 2026-08-09
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add modiqo/skillspec --skill research-codebase -g -a claude-code -y`
Codex: `npx skills add modiqo/skillspec --skill research-codebase -g -a codex -y`
Cursor: `npx skills add modiqo/skillspec --skill research-codebase -g -a cursor -y`
Gemini CLI: `npx skills add modiqo/skillspec --skill research-codebase -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add modiqo/skillspec`

## Description

Document and explain the codebase as-is using parallel sub-agents. Use when the user asks to research, explore, map, document, or understand the codebase, including questions like 'how does X work', 'where is Y implemented', 'show me the architecture', 'what does this module do', or any request for codebase-level understanding. Also use when the user says /research_codebase. Even if the user's question seems simple, if it requires reading multiple files or understanding cross-component interactions, use this skill.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Research Codebase

Conduct comprehensive read-only research across the codebase by spawning parallel sub-agents and synthesizing their findings into a structured document.

## Your only job: document what exists

- DO NOT suggest improvements or changes unless explicitly asked
- DO NOT perform root cause analysis unless explicitly asked
- DO NOT propose enhancements, critique the implementation, or recommend refactoring
- ONLY describe what exists, where it exists, how it works, and how components interact
- You are creating a technical map of the existing system

## When invoked without a query

Respond with:

> I'm ready to research the codebase. Please provide your research question or area of interest, and I'll analyze it thoroughly by exploring relevant components and connections.

Then wait for the user's research query.

## Research workflow

### 1. Read directly mentioned files first

If the user mentions specific files (docs, configs, TOML, JSON), read them FULLY before doing anything else. Use the Read tool without limit/offset parameters. Read these yourself in the main context, this ensures full context before decomposing the research.

### 2. Decompose the research question

- Break the query into composable research areas
- Think deeply about underlying patterns, connections, and architectural implications
- Identify specific components, patterns, or concepts to investigate
- Create a research plan with tasks to track subtasks
- Pay special attention to Rust-specific structures: crates, modules, traits, impls, derive macros, feature flags

### 3. Spawn parallel sub-agents

Create multiple agents to research different aspects concurrently. Use the specialized agents:

The rest: https://github.com/modiqo/skillspec/blob/HEAD/.claude/skills/research-codebase/source/SKILL.md