What problem does it solve? Hard-to-test static calls like DateTime.Now, File.*, and new HttpClient() are scattered across C# codebases, making unit testing painful. This Skill audits your code, counts every static call site, and ranks them so you know exactly where testability debt lives and what to fix first. ## Core Features & Use Cases - Static Dependency Detection: Scans .cs files for six categories of untestable statics — time, file system, environment, network, console, and process. - Ranked Report: Produces a category summary, top 10 patterns by frequency, most affected files, and a migration priority list with recommended .NET abstractions like TimeProvider and System.IO.Abstractions. - Scoped Scanning: Accepts a single file, directory, .csproj, or .sln, automatically excluding obj/, bin/, and test projects. - Use Case: Before adding unit tests to a legacy ASP.NET Core service, run the scan on the solution to discover that DateTime.UtcNow appears 28 times across 14 files, then plan a TimeProvider migration. ## Quick Start Scan my C# solution for hard-to-test static dependencies and show me a ranked report of the most frequent patterns.