File Change Impact Assessor

File Change Impact Assessor MCP Connector for Claude

A+

Quantifies the blast radius and risk of file modifications through deterministic dependency tracing.

3 tools Official Updated Oct 1, 2026 Official Vinkius Partner

The File Change Impact Assessor is a deterministic tool designed to prevent regressions by quantifying the 'blast radius' of any file modification. By parsing import statements and building a dependency graph, it identifies exactly which files are transitively affected when a target is modified, deleted, or renamed. Use analyze_impact to determine the risk level and affected files, get_dependency_graph to visualize connections, and identify_test_coverage to pinpoint the specific tests required to validate a change.

dependency-tracingblast-radiusregression-preventiondevopsimpact-analysis

3 tools expose this connector's capabilities to your AI agent.

get_dependency_graph

Retrieves a structural view of how files are connected via imports

identify_test_coverage

Pinpoints specific test files that cover the logic of the target file

analyze_impact

Determines the scope and risk of a proposed file change

See how to talk to your AI agent using File Change Impact Assessor.

What is the impact of modifying src/engine/index.ts?

The impact radius is 12 files. The risk level is HIGH because src/engine/index.ts is a core module. Affected files include src/agents/tool.ts and several view components.

Show me the dependency connections for the current project.

The dependency graph shows a central hub in src/engine/index.js with multiple downstream importers in src/agents/ and src/views/.

Which tests should I run if I change src/agents/tool.ts?

You should run src/agents/tool.test.ts and src/engine/index.test.ts to ensure full coverage.

The impact radius is calculated by counting the unique files in the transitive dependency tree that import the target file or its importers.

Related Connectors