impact-assessment

Analyze C# symbol change blast radius within a Roslyn MCP workspace.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill impact-assessment-darylmcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impact-assessment
Source: https://github.com/darylmcd/Roslyn-Backed-MCP/tree/main/skills/impact-assessment
Command: npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill impact-assessment-darylmcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-change blast-radius analysis for a C# symbol to understand the ripple effects of edits before touching code, enabling safer refactors and change planning.

Core Features & Use Cases

  • Quantifies direct references, semantic consumers, polymorphic impact, and mutation sites to rank change safety.
  • Supports rename, signature change, and delete scenarios with per-file and per-project risk assessment.
  • Use case: plan a GetUser rename by understanding where overrides, implementations, or consumers exist and where targeted follow-ups are needed.

Quick Start

Identify a symbol name (and optional change type) to obtain a ranked verdict and precise follow-up locations.

Frequently Asked Questions about impact-assessment

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

FAQPage Schema
How do I analyze the blast-radius impact of a C# code change before refactoring?

Blast-radius impact analysis identifies references, consumers, and polymorphic relationships for a proposed symbol change in a Roslyn workspace. It quantifies direct references and mutation sites to determine safe-to-change scope for renames, signature changes, or deletions.

What is the best way to assess the ripple effects of deleting a symbol in a C# project?

Assessing ripple effects involves running baseline analyses on a loaded Roslyn workspace to locate the symbol and aggregate findings. This generates a structured report with per-file and per-project severity rankings to highlight targeted follow-up locations needed for safe deletions.

Does this impact analysis support evaluating signature changes and polymorphic overrides?

Yes, this impact analysis supports rename, signature change, and delete scenarios. It evaluates polymorphic impact by locating overrides and implementations, ranking change safety by quantifying direct references and semantic consumers across the loaded workspace.

Can I use Roslyn MCP to find all consumers and mutation sites for a method rename?

Yes, you can use Roslyn MCP to load the workspace, locate the target method symbol, and run baseline analyses. The workflow aggregates per-file and per-project findings, providing a ranked verdict and precise follow-up locations for the rename.

What limitations exist when forecasting code-change impact for large C# solutions?

The analysis operates within a loaded Roslyn MCP workspace, meaning findings depend on the loaded solution's scope. It focuses on C# symbols and requires the full impact workflow to accurately determine safe-to-change scope and aggregate structured severity reports.