detect-static-dependencies

This skill identifies hard-to-test static dependencies in C# code by scanning for calls to untestable static APIs such as DateTime.Now and File.*. It generates a ranked report by frequency to help prioritize which statics to wrap for better testability.

Run a directory, project, or solution scan to audit C# code for untestable static method calls. The tool excludes obj and bin directories by default and outputs a frequency-ranked report of static call sites to improve testability.

A static dependency in C# is a call to a static API like DateTime.Now or File.* that is difficult to mock in unit tests. Identifying and wrapping these static dependencies improves code testability by allowing you to inject mock values during testing.

Yes, you can scan an entire Visual Studio solution. The skill supports file, directory, project, and solution scans for static dependencies, automatically excluding obj and bin directories by default to focus on actual source code.

Run the skill with your target path, for example: detect-static-dependencies /path/to/project. This initiates the scan and generates a ranked report of static call sites to help you prioritize wrapping untestable static APIs.

Yes, the static dependency scan automatically skips obj and bin directories by default during file, directory, project, and solution scans. This ensures only your actual source code is analyzed for untestable static API calls.