context-map

To map codebase dependencies before refactoring, generate a context map to locate files requiring modification, surface direct imports, and identify related tests. This prevents blind edits and reduces regression risks by providing a clear, reviewable overview of all affected artifacts.

The best way to identify related tests for a code change is to run a context map analysis. It detects test and reference patterns across your codebase, listing existing tests that need updates and highlighting similar implementation patterns to follow during development.

Assess the risk of breaking changes by generating a context map that summarizes potential migration needs, configuration impacts, and direct dependency relationships. This provides a concise risk assessment of your codebase before you begin implementation.

Yes, you can analyze imports and reference patterns without writing new code by generating a context map. It identifies direct dependencies and surfaces similar code patterns to follow, explicitly avoiding implementation until you review the complete file and artifact map.

Generating a context map does not modify existing source files. It strictly performs file discovery, dependency identification, and risk assessment to map relevant artifacts, avoiding any implementation until you review the generated map.