Before you refactor that function or rename that class, this skill shows you exactly what will break. It uses GitNexus to trace dependencies upstream and downstream, categorizing risk by depth: d=1 means direct callers that will definitely break, d=2 is likely affected, d=3 needs testing. You can run impact analysis on specific symbols or scan your staged git changes to see what processes and execution flows you're about to affect. The workflow is straightforward: query the target, review the blast radius starting with depth 1, check affected processes, assess risk level. It's basically a pre-commit safety net that saves you from finding out about breaking changes through bug reports.
npx skills add https://github.com/abhigyanpatwari/gitnexus --skill gitnexus-impact-analysis