migrate-static-to-wrapper

Refactoring static method calls in .NET for dependency injection involves replacing static dependencies like DateTime.UtcNow with injected wrapper interfaces. This Skill automates transforming static calls to wrapper abstractions and updates constructor injection to improve testability.

The best way to replace static file system calls in C# is migrating them to wrapper abstractions using System.IO.Abstractions. This Skill refactors static calls like File.ReadAllText to injected interfaces, enabling mockable file system operations for unit testing.

Yes, migrate-static-to-wrapper supports incremental migration across a namespace. It operates on bounded scopes including single files, projects, or namespaces, allowing you to gradually refactor static dependencies to wrapper abstractions without overhauling the entire solution.

You can use Microsoft.Bcl.TimeProvider to test static DateTime calls in .NET 8 by abstracting time dependencies. This Skill replaces DateTime.UtcNow with TimeProvider abstractions and leverages Microsoft.Extensions.TimeProvider.Testing for deterministic unit testing.

Setting up static refactoring for testability requires Microsoft.Bcl.TimeProvider, System.IO.Abstractions, and their testing helper libraries. The Skill requires dependency injection setup in your .NET 8+ project to properly resolve the injected wrapper interfaces.

You should avoid replacing static calls with wrapper abstractions if your .NET project lacks dependency injection setup or targets a version below .NET 8. The Skill relies on Microsoft.Bcl.TimeProvider support and bounded scopes to function correctly during static refactoring.