Unity Refactor

Refactor Unity C# codebases safely by detecting code smells, prioritizing them by risk, and decomposing monolithic managers into modular services incrementally while preserving behavior. Execute one isolated change at a time and verify compilation before proceeding to the next step.

Common Unity code smells in monolithic managers include tightly coupled cross-cutting concerns. This skill scans your C# codebase to surface actionable smells and ranks them by risk, enabling a structured, prioritized plan for progressive decoupling into focused services.

Yes, incremental refactoring supports mid-size Unity projects transitioning from a mega-manager pattern to modular services like score, spawn, and save. It presents a complete prioritized plan before modification and enforces strict safety rules to ensure gameplay behavior remains unaltered.

The best way to ensure safe C# refactoring in Unity is to implement one isolated change at a time, then validate compilation and references before proceeding. This skill enforces strict safety rules and requires a workflow to verify compilation after each incremental modification.

You need a Unity project with C# scripts and a workflow to verify compilation after each incremental change. The skill scans your project root to generate a prioritized refactoring plan based on detected code smells before any modifications are made.

Reference-driven recipes standardize refactoring outcomes across multiple Unity projects. By linking to documented recipes, the skill ensures continuity and consistency when decomposing monolithic managers and cross-cutting concerns into focused, modular services.