request-context-gatherer

Prevent regressions during refactoring by systematically reviewing all related files, including imports, callers, and tests, before executing any code modification. This impact analysis traces call chains to identify dependencies, avoiding unintended consequences and maintaining system integrity.

Code impact analysis is the process of reviewing all files affected by a modification request, including direct targets, imports, and callers. You need it before any code change scenario to prevent blind edits and ensure complete understanding of dependencies and expected caller behavior.

Check for affected callers and dependencies by following a systematic workflow that reads target files, identifies consumers, and traces call chains. This ensures all imports and tests covering the function are reviewed before execution, preventing unexpected downstream breaks.

Yes, this impact analysis approach applies to any code change scenario requiring modification. It systematically analyzes direct target files, imports, callers, and tests regardless of context, ensuring system integrity by preventing unintended consequences across the entire codebase.

The best way to review related files is using a systematic step-by-step process that reads direct targets, maps imports, identifies callers, and checks tests. This comprehensive impact analysis prevents blind code edits by ensuring full contextual understanding before execution.