godot-refactor

Refactoring Godot scripts involves detecting code-created objects and tight coupling, then converting them into modular components using a scene-first, signal-driven architecture. This process preserves exact behavior while building a reusable component library.

Scene-first architecture in Godot prioritizes base scenes and reusable components over code-created objects. You need it when your project suffers from tight coupling via get_node or has inline data that should be extracted into resource presets and modular components.

Extracting inline data into resource presets is part of the Data operation in automated Godot refactoring. The process identifies inline data structures and converts them into reusable resource presets stored under a growing component library directory.

Yes, automated Godot refactoring preserves exact behavior by using a four-phase process with automatic validation and optional rollback. Per-operation commits ensure git-backed safe changes, allowing auto-rollback if any behavior changes are detected during verification.

Yes, this refactoring process is designed for Godot 4.x projects. You can run it directly in Claude Code to automatically analyze and refactor anti-patterns like tight coupling and code-created objects with a single approval.

Decoupling Godot scripts with signals is handled through the Signals operation, which replaces tight coupling via get_node or has_method with signal-driven communication. This creates modular components that interact through signals rather than direct node references.