impact-analysis

Analyze TypeScript symbol change impact using blast radius and dependency tools.

12|1|Updated Feb 20, 2026

Search Tags:#code quality #typescript #refactoring #dependency analysis #impact analysis #blast radius

Ready to run

npx skills add https://github.com/guyowen/typegraph-mcp --skill impact-analysis-guyowen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: impact-analysis
Source: https://github.com/guyowen/typegraph-mcp/tree/main/skills/impact-analysis
Command: npx skills add https://github.com/guyowen/typegraph-mcp --skill impact-analysis-guyowen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers understand the potential consequences of modifying a piece of TypeScript code by analyzing its reach and dependencies across a codebase.

Core Features & Use Cases

Blast Radius Calculation: Identifies all direct callers and affected files for a given symbol.
Transitive Dependency Mapping: Shows how many packages are affected by a change.
Module Coupling Analysis: Assesses the interconnectedness of code modules to gauge refactoring risk.
Use Case: Before refactoring a core utility function, use this Skill to determine how many other parts of the system rely on it, and whether those dependencies span multiple packages.

Quick Start

Analyze the impact of changing the TenantId symbol in the file packages/core/src/schemas/ids.ts.

Frequently Asked Questions about impact-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I assess the blast radius of changing a TypeScript symbol?▼

To assess the blast radius of a TypeScript symbol, you analyze its direct callers and affected files. This process identifies all transitive dependencies and affected packages to gauge the overall reach of the modification.

What is the best way to measure module coupling before refactoring TypeScript code?▼

Measuring module coupling before refactoring TypeScript involves analyzing the interconnectedness of your code modules. This analysis reveals how many packages rely on a specific symbol and highlights the potential risk of modifying widely-used utilities.

How do I find all dependents of a TypeScript function across packages?▼

Finding all dependents of a TypeScript function across packages requires mapping its transitive dependencies. This mapping shows exactly how many packages are affected by a change and whether those dependencies span multiple module boundaries.

Can I analyze the impact of modifying widely-used TypeScript schemas?▼

Yes, you can analyze the impact of modifying widely-used TypeScript schemas by calculating their blast radius. This identifies all direct callers and affected files, showing exactly what relies on that schema before you change it.

When do I need transitive dependency mapping for code changes?▼

You need transitive dependency mapping for code changes when modifying a core utility function used across a codebase. It shows how many packages are affected by a change, helping determine if dependencies span multiple module boundaries before refactoring.

Does TypeScript impact analysis work for assessing refactoring risk?▼

Yes, TypeScript impact analysis works for assessing refactoring risk by combining blast radius, dependents, and module boundary analysis. This comprehensive assessment reveals the interconnectedness of modules and the potential consequences of modifying code.