agent-investigator

You can investigate codebase architecture by running a read-only analysis that traces data flow and maps blast radius without writing to disk. It generates a structured investigation brief containing evidence-backed findings for architects and engineers.

A codebase investigation brief is a structured report that explains feature behavior, data flow, and potential blast radii. You need one when decision-makers must understand code context and risk before approving changes.

To map blast radius, the investigator performs a read-only analysis of the codebase to trace data flow and feature behavior. It then outputs a structured brief detailing the potential impact without executing any repository changes.

Yes, you can extract code context and analyze repository risk in a strictly read-only mode. The process evaluates feature behavior and traces data flow to produce evidence-backed findings without modifying the repository.

Codebase investigation supports understanding feature behavior in large codebases by tracing data flow and mapping blast radius. It provides architects with a structured brief to navigate complexity without executing changes.

The limitation of read-only codebase investigation is that it does not modify the repository or write to disk. It strictly produces structured briefs with evidence-backed findings, meaning it cannot execute or apply code changes.