refactor-to-standards

Refactoring code to match project conventions requires diagnosing deviations against established patterns like constructors, mapping, and DI registration. The skill enforces strict guardrails to prevent business-logic changes, applying updates only after per-file confirmation.

Standardizing dotnet minimal APIs and application services involves checking endpoint conventions, dependency injection registration, and SOLID boundaries. The skill diagnoses these areas per-file and applies refactors through a keep/undo workflow to ensure compliance.

Yes, you can use staged files to apply code standards refactoring. The skill detects files modified in staging or accepts user-provided files, generating per-file diagnostic reports before requesting confirmation to write any changes.

Ensuring logging style and clean architecture boundaries during refactoring requires diagnosing code against project patterns and SOLID principles. The skill checks logging conventions and architectural boundaries, offering an undo option per file to prevent unwanted edits.

Automated code refactoring for dependency injection and validators is limited by strict guardrails: it avoids creating new artifacts, blocks sensitive config access, and prevents unrequested test changes. It focuses solely on standardization rather than adding new features or fixing bugs.