rubberduck-change-impact-pro

To analyze code change impact, you need evidence-governed semantic analysis that identifies affected callers, callees, shared state, and required tests. This Skill processes your repository and inputs like target, change type, and branch to map these relationships accurately.

Evidence-governed change impact analysis uses full semantic codebase intelligence and dual-source adjudication to identify what breaks when you modify a function, file, or symbol, ensuring accurate detection of affected callers and migration order.

Finding affected callers and callees requires full semantic codebase intelligence. By evaluating your target, change type, and branch, the analysis maps shared state dependencies and identifies exactly what breaks upstream and downstream.

Yes, change impact analysis requires access to your code repository and specific inputs including the target symbol, change type, branch, and migration window to accurately identify optimization opportunities and shared state.

Determining migration order involves analyzing shared state and semantic dependencies across your branch. By setting a migration window and target, the analysis evaluates the change type to sequence your migration steps safely.

Yes, you can identify which tests to run by performing evidence-governed change impact analysis. It evaluates the semantic relationships of your target change to pinpoint exactly which affected callers and shared state require testing.