code-archaeology

To map unfamiliar codebases, systematically investigate project structure, entry points, and dependencies to build an architectural overview. This read-only analysis identifies frequently changed files using repository history and traces data flow to produce evidence-based architecture summaries.

Analyzing legacy code for refactoring requires tracing architectural relationships and identifying frequently modified files via git history. This approach highlights safe modification zones and produces an evidence-based summary of the system's design patterns and data flow before development.

Yes, repository exploration allows you to trace data flow and identify hot files by analyzing git history and structural relationships. This read-only investigation workflow reveals frequently changed modules and core architectural patterns within the target codebase.

Getting an architecture summary during onboarding involves systematically mapping the project structure, entry points, and module dependencies. This read-only process highlights key files and design patterns, creating a safe overview of where changes should be made.

Codebase analysis works for identifying entry points and module dependencies by systematically investigating the project structure. It traces architectural relationships and data flow to map out how different components interact within the system.

Read-only codebase investigation workflows should not be used when you need to modify code directly or execute runtime tests. This approach is strictly for mapping architectural relationships, tracing data flow, and producing evidence-based summaries before actual development changes.