This skill helps an agent compose Godot 4.7 games from small reusable scenes, instance them at runtime and reach nodes without crashing on freed or missing ones. It starts by reading project.godot for the main scene and autoload list, and the .tscn files for the node tree.
It includes patterns for instancing a scene with correct local positions, safe node access with $, unique names and get_node_or_null, an autoload singleton, and changing the running scene. A bundled read-only Python checker reports missing or wrong-case res:// paths, undeclared resource ids, bad parent paths and stale uid sidecar files, and needs no Godot binary.
What You Get
- A core workflow from reading project.godot and scenes to instancing, safe node access, autoloads and queue_free()
- GDScript patterns for instancing a bullet, safe $ and % access, an autoload singleton and a scene change
- A Python project checker that lists errors and warnings for broken references, with a JSON output mode
- A gotcha list covering null paths, mid-frame free, add_child timing, autoload order, deferred scene changes and moved files
Common Use Cases
- Spawning bullets, enemies or UI scenes at runtime
- Debugging a $Path or get_node() call that returns null
- Repairing references after files were moved or renamed outside the editor
- Registering a game state singleton as an autoload
What Makes It Unique
The skill ships a read-only checker that understands Godot’s uid-first loading, so it separates real errors from stale paths Godot can still recover. It checks case differences that work on Windows and macOS but break on Linux and in exported packs. The other Godot skills in the repository call this checker after they add or move scenes.
Under The Hood
The agent loads the SKILL.md and, when needed, a reference on saving scenes built in code, scene inheritance and deferred tree changes. It then runs a local Python script that reads your project’s text files, such as scenes, resources, scripts and project.godot, and prints findings; its own description says it is read-only, never edits anything and needs no Godot binary. It uses only the Python standard library and no network. Optionally the agent also runs the Godot binary headless on a scene for a few hundred frames, with the log redirected to a file and searched with grep, which writes a log file in your project.