detect-static-dependencies Skill
Scan C source files for hard-to-test static dependencies — DateTime.Now/UtcNow, File., Directory., Environment., HttpClient, Console., Process., and other untestable statics. Produces a ranked report of static call sites by frequency. USE FOR: find untestable statics, scan for static dependencies, testability audit, id Published by microsoft in testfx.
What is detect-static-dependencies Skill?
Scan C source files for hard-to-test static dependencies — DateTime.Now/UtcNow, File., Directory., Environment., HttpClient, Console., Process., and other untestable statics. Produces a ranked report of static call sites by frequency. USE FOR: find untestable statics, scan for static dependencies, testability audit, id Published by microsoft in testfx. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Security review
- Testing use cases
- Security review use cases
Technical details
- Install or run with Copy skill directory
When to use detect-static-dependencies Skill
- Use it for testing.
- Use it for security review.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/testfx
- Skill file: .agents/skills/detect-static-dependencies/SKILL.md
What it does
Scan C source files for hard-to-test static dependencies — DateTime.Now/UtcNow, File., Directory., Environment., HttpClient, Console., Process., and other untestable statics. Produces a ranked report of static call sites by frequency. USE FOR: find untestable statics, scan for static dependencies, testability audit, id
Skill instructions
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
Explore related resources
Frequently asked questions
What is detect-static-dependencies?
detect-static-dependencies is a open-source AI agent skill with Copy skill directory. Scan C source files for hard-to-test static dependencies — DateTime.Now/UtcNow, File., Directory., Environment., HttpClient, Console., Process., and other untestable statics.
Who is detect-static-dependencies best for?
detect-static-dependencies is best for reusing agent instructions, scripts, and references, testing workflows, security review workflows.
How do I install detect-static-dependencies?
Install or run detect-static-dependencies using Copy skill directory. Check detect-static-dependencies for the latest setup command.
Is detect-static-dependencies actively maintained?
detect-static-dependencies may need a closer maintenance check before production use.
Auto-fetched from GitHub.
