migrate-static-to-wrapper Skill
Mechanically replace static dependency call sites with wrapper or built-in abstraction calls across a bounded scope (file, project, or namespace). Performs codemod-style bulk replacement of DateTime.UtcNow to TimeProvider.GetUtcNow(), File.ReadAllText to IFileSystem, and similar transformations. Adds constructor inject Published by microsoft in testfx.
What is migrate-static-to-wrapper Skill?
Mechanically replace static dependency call sites with wrapper or built-in abstraction calls across a bounded scope (file, project, or namespace). Performs codemod-style bulk replacement of DateTime.UtcNow to TimeProvider.GetUtcNow(), File.ReadAllText to IFileSystem, and similar transformations. Adds constructor inject 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
- Testing use cases
Technical details
- Install or run with Copy skill directory
When to use migrate-static-to-wrapper Skill
- Use it for testing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/testfx
- Skill file: .agents/skills/migrate-static-to-wrapper/SKILL.md
What it does
Mechanically replace static dependency call sites with wrapper or built-in abstraction calls across a bounded scope (file, project, or namespace). Performs codemod-style bulk replacement of DateTime.UtcNow to TimeProvider.GetUtcNow(), File.ReadAllText to IFileSystem, and similar transformations. Adds constructor inject
Skill instructions
Migrate Static to Wrapper Perform mechanical, codemod-style replacement of static dependency call sites with calls to injected wrapper interfaces or built-in abstractions. Operates on a bounded scope (single file, project, or namespace) so migrations can be done incrementally. When to Use - After wrappers have been generated (via generate-testability-wrappers) or built-in abstractions identified - Migrating DateTime.UtcNow → TimeProvider.GetUtcNow() across a project - Migrating File. → IFileSystem.File. across a namespace - Adding constructor injection for the new abstraction to affected classes - Incremental migration: one project or namespace at a time When Not to Use - No wrapper or abstraction exists yet (use generate-testability-wrappers first) - The user wants to detect statics, not migrate them (use detect-static-dependencies) - The code does not use dependency injection and the user hasn't chosen ambient context - Migrating between test frameworks (use the appropriate migration
Explore related resources
Frequently asked questions
What is migrate-static-to-wrapper?
migrate-static-to-wrapper is a open-source AI agent skill with Copy skill directory. Mechanically replace static dependency call sites with wrapper or built-in abstraction calls across a bounded scope (file, project, or namespace).
Who is migrate-static-to-wrapper best for?
migrate-static-to-wrapper is best for reusing agent instructions, scripts, and references, testing workflows.
How do I install migrate-static-to-wrapper?
Install or run migrate-static-to-wrapper using Copy skill directory. Check migrate-static-to-wrapper for the latest setup command.
Is migrate-static-to-wrapper actively maintained?
migrate-static-to-wrapper may need a closer maintenance check before production use.
Auto-fetched from GitHub.
