domains / families / software-engineering / detect-static-dependencies

detect-static-dependencies

separate

ACTIVATION PREREQUISITE: the request or discovered target must explicitly identify C#, .NET, `.cs`, or `.csproj`; otherwise stay dormant without invoking this skill. USE FOR: locating System.DateTime.Now/UtcNow, System.IO.File/Directory, System.Environment, HttpClient, Console, or Process usage in C#; auditing C# code for hard-to-test framework dependencies; or verifying those C# calls are already abstracted. DO NOT USE FOR: any target lacking the activation prerequisite; generating wrappers (use generate-testability-wrappers); migrating code (use migrate-static-to-wrapper); or general code review.

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

When not to use

• The user wants wrappers generated (hand off to `generate-testability-wrappers`)
• The user wants mechanical migration done (hand off to `migrate-static-to-wrapper`)
• The statics are already behind interfaces or `TimeProvider`
• The code is not C# / .NET

Skill page

Source