What problem does it solve?
Provide a structured, discoverable analysis of which code elements and tests will be affected by planned refactors, interface or signature changes, file moves, renames, merges, or cross-module modifications to reduce the risk of missed updates.
Core Features & Use Cases
- Change identification: Clarify the core change target (for example, a method signature, interface, or class rename).
- Affected list generation: Enumerate direct implementers/inheritors, direct callers (including tests), and likely indirect dependents that may require updates.
- Output for planning: Produce a human-readable impact table that shows relationship type and recommended adjustments, and mark any dynamic or reflection-based usages as "requires manual confirmation".
- Use case: Use during design or planning discussions to decide whether a proposed interface change is feasible and to scope work for implementation and testing.
Quick Start
Ask the skill to generate a context map by describing the proposed change (for example the method, interface, or file being modified) and the intended scope.