This one's built for when Godot throws cryptic errors at you and you need to understand what actually went wrong. It covers the common culprits: parser errors from missing colons or bad indentation, null reference crashes, array index issues, and those annoying "can't change state while flushing queries" physics errors. The skill includes concrete code examples showing both the wrong and right way to handle signals, node paths, and deferred calls. It's most useful when you're staring at a stack trace or error message and need someone to translate what it means and show you the fix. Solid reference material for both Godot 3 and 4 patterns.
npx skills add https://github.com/zate/cc-godot --skill godot-debugging