What problem does it solve? Before editing code, developers need to know what will break. This Skill answers questions like "Is it safe to change this function?" by tracing upstream dependencies, mapping affected execution flows, and assigning a risk level to proposed changes. ## Core Features & Use Cases - Blast Radius Analysis: Runs impact queries with configurable direction, depth, and confidence thresholds to list direct callers (d=1, will break) through transitive dependents (d=3). - Execution Flow Mapping: Reads GitNexus process resources to identify which runtime flows (e.g., LoginFlow, TokenRefresh) touch the target symbol. - Pre-Commit Risk Checks: Uses detect_changes on staged git diffs to map pending changes to affected flows and produce a LOW/MEDIUM/HIGH/CRITICAL risk rating. - Use Case: Before renaming a shared validation function, run an upstream impact query to find its direct callers, check affected auth processes, and report a MEDIUM risk with the exact files that need updates. ## Quick Start Ask the agent to analyze what will break if you change a specific function, for example by requesting an impact analysis of validateUser before editing it.
