What problem does it solve?
This Skill helps developers and reviewers determine what will break or be affected when changing code by mapping symbol-level dependencies and execution flows to assess risk before editing or committing changes.
Core Features & Use Cases
- Dependency Blast Radius: Identify direct and transitive dependents of a target symbol with confidence scores and depth levels (d=1, d=2, d=3) so teams can prioritize testing and code review.
- Pre-commit Change Detection: Map staged or uncommitted changes to affected processes and flows to flag high-risk edits before they reach the repository.
- Risk Assessment & Reporting: Summarize impact as LOW/MEDIUM/HIGH/CRITICAL based on affected symbols, processes, and whether the change touches critical paths like auth or payments.
- Use Case: Before refactoring validateUser, run an impact analysis to list WILL BREAK direct callers, identify affected login and token flows, and decide whether to gate the change behind tests or a rollout.
Quick Start
Run an impact analysis for the symbol validateUser, list d=1 direct callers and processes that will break, and provide a concise risk level and recommended mitigation.