What problem does it solve? Brownfield .NET codebases rarely document their actual responsibility split, so before changing code you must derive structure, dependency direction, DI lifetimes, implicit runtime bindings, and change impact from code evidence. This Skill performs that investigation systematically and produces a reviewable Markdown change-analysis note instead of an opaque one-shot answer. ## Core Features & Use Cases - Structure and impact analysis: Extracts the de-facto responsibility split, entry points, DI registrations and lifetimes, pipeline ordering rules, convention-based discovery, and implicit runtime bindings (XML/config strings, reflection names, route tokens) from C# solutions. - Grep-first impact boundaries: Separates the review boundary (all references to a changed entity) from the must-change boundary (sites the change actually breaks), with a deterministic Roslyn-based structure pack reserved for grep-weak questions like DI captive dependencies and attribute values. - Prohibited-changes list and handoffs: Derives evidence-backed silent-breakage prohibitions from extracted local rules, and routes defect-level findings to csharp_review and security gaps to security_review. - Use Case: Before adding a required constructor parameter to a service in an unfamiliar ASP.NET solution, run this Skill to get the full reference surface, the sites that break, the DI lifetime risks, and a change placement basis for the design phase. ## Quick Start Ask the AI to run the dotnet_change_analysis skill on your solution path with your change request, for example: analyze the repository at ./src for the change 'add a required tenantId parameter to OrderService' and produce a change-analysis note.
