godot-debugging-profiling — Claude Code skill for Godot debugging

What godot-debugging-profiling does

The skill walks the agent through a symptom → monitor → script path. Memory that climbs while nodes are removed, ObjectDB growth, GPU spikes in the Visual Profiler, headless builds exiting with the wrong code, corrupted logs from thread races — each symptom maps to a ready GDScript file the agent drops into your project.

Roughly twenty scripts ship with it: an orphan node detector, a memory threshold alert, a scene tree dump, a microsecond benchmarker built on Time.get_ticks_usec, an automated QA suite for CI, an engine error interceptor, a thread-safe logger, custom monitors for the Debugger tab, and a remote console for mobile builds. There is also a list of things not to do. Profiling a debug build tells you nothing useful because it runs several times slower than release, and OBJECT_ORPHAN_NODE_COUNT always returns 0 in release, so a leak stays hidden.

Some techniques only work in debug builds. Engine.capture_script_backtraces(true) captures local variables and can itself keep objects from being freed, so switch it on for a narrow window. An EditorDebuggerPlugin has to be unregistered in _exit_tree(), otherwise ghost connections stay in the engine's debugging loop. The skill advises profiling release exports with V-Sync off.