What problem does it solve? Before editing code, developers often cannot tell which functions, callers, and execution flows will break. This Skill answers "is it safe to change X?" by mapping the blast radius of a symbol through the GitNexus dependency graph. ## Core Features & Use Cases - Upstream Impact Analysis: Runs gitnexus_impact to list direct callers (d=1, will break) and indirect dependents (d=2/d=3) with confidence scores. - Pre-Commit Change Detection: Uses gitnexus_detect_changes on staged git changes to map edits to affected execution processes and assign a risk level. - Risk Assessment Framework: Classifies results as LOW, MEDIUM, HIGH, or CRITICAL based on affected symbol counts, processes, and critical paths like auth or payments. - Use Case: Before renaming a shared validateUser function, run the impact workflow to discover that loginHandler and apiMiddleware call it directly and that the LoginFlow process is affected, then decide whether the change is safe. ## Quick Start Ask the assistant to check what will break if you change a specific function, for example: "What depends on validateUser and is it safe to modify it?"
