deep-survey

To analyze a TypeScript codebase architecture without manual reading, run a 7-phase deep survey using typegraph-mcp tools. It maps the structural skeleton, module anatomy, patterns, dead code, domain topology, runtime behavior, and risks to generate a detailed architectural report.

The best way to detect dead code and assess risk in a TypeScript project is executing a deep survey. It identifies high-impact areas, approximates runtime behavior, and evaluates potential propagation of changes to generate a comprehensive risk assessment report.

Yes, you can use this code analysis approach for large, unfamiliar TypeScript projects. The deep survey is specifically designed for onboarding, producing a detailed architectural report that enables rapid understanding and informed decision-making before making any code changes.

To map module boundaries and dependencies in a TypeScript codebase, execute the module anatomy phase of the deep survey. It details what each module exports, its specific dependencies, and its boundaries to clarify structural interactions.

Yes, you need to install the tsx dependency and perform a prerequisite health check using typegraph-mcp tools. The 7-phase codebase analysis requires this environment setup before making subsequent tool calls for each phase.

Beyond basic structural mapping, a deep codebase survey covers module anatomy, pattern discovery, dead code detection, domain topology, runtime behavior approximation, and risk assessment across seven distinct analysis phases.