context-map

To map code dependencies before refactoring, you need to identify direct imports, exports, and related test files. This process generates a comprehensive context map of files to modify and highlights potential breaking changes.

The best way to identify all files for a codebase change is to perform codebase analysis that locates pertinent files, recognizes existing code patterns, and maps their dependencies to ensure no critical functionality is overlooked.

To assess the risk of breaking changes before modifying code, generate a risk assessment that highlights potential impacts like required migrations or configuration needs alongside the dependency mapping of the affected files.

Finding existing test files related to a development task requires test identification, which locates all corresponding tests for the files involved in the task and ensures no critical functionality is overlooked during implementation.

Yes, you can use code analysis to perform pattern recognition, which finds similar code patterns across the codebase for guidance. This helps you understand the full scope of changes required before implementation.

Yes, impact analysis helps identify required database migrations by highlighting potential breaking changes and configuration needs. This risk assessment is included when mapping out relevant files and dependencies before implementation.