detect-static-dependencies

Detect Static Dependencies Scan a C# codebase for calls to hard-to-test static APIs and produce a ranked report showing which statics appear most frequently, which files are most affected, and which abstractions already exist in the .NET ecosystem to replace them. When to Use Auditing a project's testability before adding unit tests Understanding the scope of static coupling in a legacy codebase Prioritizing which statics to wrap first (highest-frequency wins) Creating a migration plan for incremental testability improvements Response Guidelines Scale the response to the user's request. A question about a specific category (e.g., "find time statics") should focus on that category with file locations and counts, not produce a full report across all categories. When the user provides a specific file or directory path, scan only that scope — do not expand to the entire solution unless asked. The full structured report format in Step 4 is for comprehensive audit requests. For focused questions, return only the relevant subset (e.g., category summary + affected files for the requested category). When Not to Use Show more Installs 834 Repository dotnet/skills GitHub Stars 5.1K First Seen Apr 13, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass