research-codebase

Codebase investigation involves reading relevant source files, tracing dependencies, and mapping task descriptions to specific implementation areas. The skill compiles an objective findings report with file path references to clarify how existing modules relate to the requested feature.

Tracing dependencies during debugging is done by reading source files and examining module relationships. The skill identifies how a bug maps to the current codebase by capturing relevant paths and producing an objective, non-prescriptive report of findings.

Yes, you can summarize code intent without proposing solutions. The skill provides factual, non-prescriptive reporting by mapping a task description to relevant code areas and outputting an objective findings report rather than suggesting implementation changes.

To start codebase reconnaissance, provide a task description or GitHub issue URL. The skill will examine relevant modules, capture context by mapping the request to code areas, and compile a report tracing dependencies and file relationships.

Yes, the skill works for assessing existing implementations against new product goals. It reads source files and traces dependencies to map the product goal to the current codebase, producing an objective findings report detailing relevant relationships.