repo-map-zoom-out

To map unfamiliar code areas, identify entry points, trace callers, analyze data flow, and locate ownership boundaries. This reveals likely edit surfaces and validation paths, preparing you for risky changes by clarifying subsystem architecture and dependencies.

Tracing callers and data flow involves analyzing how data moves through the codebase and discovering dependent code. This process identifies entry points like APIs, routes, commands, and event handlers, revealing the full dependency graph of a subsystem.

ADR analysis is needed when preparing for risky changes or understanding an architecture boundary. Locating relevant Architecture Decision Records alongside tests and fixtures provides context on validation rules and design decisions governing the target code area.

Yes, repo mapping identifies entry points such as APIs, routes, jobs, and event handlers while simultaneously locating validation commands and tests. This provides a comprehensive overview of the target code area's operational surface and verification methods.

Code analysis works for identifying likely edit surfaces by inspecting documentation and tracing data flow alongside callers. It maps out the specific areas requiring modification, ensuring you understand the full impact of changes on the subsystem.