blast-radius

# Blast Radius Analysis Analyze the impact of current code changes using the code knowledge graph. ## Prerequisites This skill requires the **gauntlet** plugin for graph data. Check if it's available: ```bash GRAPH_QUERY=$(find ~/.claude/plugins -name "graph_query.py" -path "*/gauntlet/*" 2>/dev/null | head -1) ``` **If gauntlet is not installed** (GRAPH_QUERY is empty): Fall back to a manual impact analysis using `git diff` and `grep` to trace imports and call sites. Skip graph steps and go directly to step 3 (manual mode). **If gauntlet is installed but no graph.db exists**: Tell the user: "Run `/gauntlet-graph build` first." ## Steps 1. **Show current changes**: Run `git diff --stat` to show the user what files changed. 2. **Run impact analysis** (requires gauntlet): ```bash python3 "$GRAPH_QUERY" \ --action impact --base-ref HEAD --depth 2 ``` **Fallback tier 1 (sem available, no gauntlet)**: Use sem for cross-file dependency tracing: ```bash if command -v sem &>/dev/null; then sem impact --json <changed-file> fi ``` This traces real function-level dependencies instead of filename matching. See `leyline:sem-integration` for detection patterns. **Fallback tier 2 (no sem, no gauntlet)**: Trace callers of changed functions with rg (or grep): ```bash # Prefer rg for speed; fall back to grep if command -v rg &>/dev/null; then git diff --name-only HEAD | while read f; do stem="${f%.*}"; st...