godot-extract-to-scenes

To convert code-created Godot nodes into reusable scenes, this Skill detects .new() instantiation patterns in GDScript and generates corresponding .tscn scene files. It updates parent scripts with @onready references and builds a component library for scalable architecture.

Instantiating Godot nodes with .new() in GDScript reduces editor visibility because dynamically created nodes are not represented as reusable .tscn scenes in the editor hierarchy. This leads to brittle architectures and prevents visual component management.

The best way to refactor dynamic Godot nodes into a component library is to extract code-created instances like Timer.new() or Area2D.new() into standalone .tscn scene files. This enables scene-based organization and clean refactoring across Godot projects.

Yes, the scene extraction process modifies existing GDScript parent scripts by replacing dynamic .new() instantiation patterns with @onready references. This allows scripted code to seamlessly interact with the newly generated scene-backed components.

Yes, you can automate Git commits when extracting Godot nodes to scenes. This Skill performs automated Git commits per extraction, ensuring version control safety while generating .tscn files and updating GDScript references.

You should avoid extracting dynamically created nodes into Godot scenes if your project relies heavily on highly volatile runtime instances that do not fit a reusable component library pattern, as generating .tscn files for unique transient nodes adds unnecessary overhead.