Menu
Analyze the impact of changing a TypeScript symbol by combining blast radius, dependents, and module boundary analysis. Trigger when asking what will break, assessing change risk, or before modifying widely-used symbols.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Efficiently explore unfamiliar TypeScript code using navigation tools instead of reading entire files. Trigger when asking how something works, exploring a new module, understanding architecture, or tracing request flows.
Run a comprehensive 7-phase codebase analysis using all typegraph-mcp tools, producing a detailed architectural report. Trigger when onboarding to an unfamiliar codebase, requesting a full architectural overview, asking for a codebase health report, or needing to understand the overall structure before making significant changes.
Select the right typegraph-mcp tool for TypeScript navigation. Trigger when finding definitions, references, types, exploring code structure, preparing refactors, or any task where you would otherwise use grep/glob for TypeScript symbols.
Audit module dependencies to find circular imports, analyze coupling, and understand dependency structure. Trigger when asking about circular deps, module structure, package coupling, or evaluating module boundaries.
Verify a refactor is safe before making changes. Trigger when renaming, moving, or restructuring TypeScript modules, extracting code into new modules, or changing interfaces and service definitions.
| name | impact-analysis |
| description | Analyze the impact of changing a TypeScript symbol by combining blast radius, dependents, and module boundary analysis. Trigger when asking what will break, assessing change risk, or before modifying widely-used symbols. |
Analyze the impact of changing a TypeScript symbol by combining blast radius, dependents, and module boundary analysis.
Call ts_blast_radius with the file and symbol to get direct callers and affected files.
Call ts_dependents on the file to see the transitive impact grouped by package. This shows whether the change is contained to one package or crosses boundaries.
Call ts_module_boundary with the affected files to understand the coupling. A low isolation score means the change is tightly coupled to external code.
Present findings as:
User: "What happens if I change the TenantId schema?"
1. ts_blast_radius({ file: "packages/core/src/schemas/ids.ts", symbol: "TenantId" })
-> 45 direct callers across 28 files
2. ts_dependents({ file: "packages/core/src/schemas/ids.ts" })
-> 158 transitive dependents across 4 packages
3. ts_module_boundary({ files: ["packages/core/src/schemas/ids.ts"] })
-> isolation score: 0.058 (highly coupled)
Report: HIGH IMPACT. 45 direct usages across 28 files in 4 packages.
The schemas module has very low isolation (0.058).
Recommend: add new schema alongside old, migrate callers incrementally, then remove old.