research

Name: research
Availability: InStock
Author: parcadei

Document existing codebase components and interactions into structured Markdown reports.

3.9k|296|Updated Dec 23, 2025

Search Tags:#architecture #documentation #research #knowledge management #codebase #technical writing

Ready to run

npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill research-parcadei

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: research
Source: https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/research
Command: npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill research-parcadei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a systematic way to document and explain an existing codebase without suggesting improvements, ensuring a clear understanding of the current system.

Core Features & Use Cases

Codebase Documentation: Generates detailed explanations of code structure, functionality, and interconnections.
Historical Context: Leverages a thoughts/ directory to provide historical context and past explorations.
Use Case: A new developer joins a project and needs to understand a specific module. They can use this Skill to get a comprehensive, objective overview of that module's implementation and its place within the larger system.

Quick Start

Use the research skill to document the authentication module.

Frequently Asked Questions about research

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

FAQPage Schema

How do I document an existing codebase without suggesting changes?▼

Documenting an existing codebase architecture involves using parallel sub-agents to explore components and interactions, explaining current implementation and file locations without suggesting changes, and synthesizing findings into structured Markdown reports with GitHub permalinks.

What is the best way to generate technical documentation for a codebase I just joined?▼

Generating technical documentation for an unfamiliar codebase is best handled by deploying specialized agents to comprehensively explore components and synthesize findings into structured Markdown, providing an objective overview of the module's implementation and system interactions.

How does parallel sub-agent research work for codebase documentation?▼

Parallel sub-agent research for codebase documentation works by deploying specialized agents like 'scout' and 'thoughts-locator' to comprehensively explore current implementations and historical context, synthesizing structured Markdown reports with GitHub permalinks.

Can I use a thoughts directory to add historical context to codebase documentation?▼

Yes, you can leverage a `thoughts/` directory to add historical context to codebase documentation. The research process uses this directory to incorporate past explorations and historical background alongside current implementation details.

Does codebase documentation include GitHub permalinks for file locations?▼

Yes, codebase documentation includes GitHub permalinks for file locations. The research process synthesizes findings into structured Markdown reports that reference exact implementation file locations using GitHub permalinks.

When should I not use automated codebase documentation?▼

You should avoid automated codebase documentation when you need code refactoring suggestions or architectural improvements, as this approach focuses strictly on explaining the current implementation objectively without recommending changes.