research_codebase

To document an existing codebase, this Skill analyzes components and identifies patterns by spawning parallel sub-agents. It synthesizes findings into detailed technical documentation, providing a clear map of the system for new developers.

Analyzing component interactions is handled by spawning parallel sub-agents that research specific code components. The Skill identifies interaction patterns and synthesizes these findings to explain how different parts of the codebase work together.

The best way to understand a specific feature is using this Skill to get a comprehensive overview of the relevant code. It explains the feature's purpose and maps its connections to other parts of the system, integrating historical context.

Yes, you can integrate historical context from a thoughts directory into codebase analysis. The Skill explicitly incorporates insights from the thoughts directory to provide a complete picture of the system's development history and design decisions.

Yes, codebase research works for explaining how specific code components work. The Skill analyzes the codebase to explain component functionality and interactions, delivering a detailed technical map of the existing system.

A limitation of using sub-agents for codebase documentation is that it relies on existing code and historical context. It synthesizes current patterns, but may not capture undocumented external dependencies or runtime behaviors not reflected in the code.