godot-debugging — Claude Code skill: install and use
Helps an agent investigate Godot errors, crashes, and unexpected behavior. Use it when a project needs a focused diagnosis of GDScript or scene issues.
npx skills add Zate/cc-godot --skill godot-debugging -a claude-codeWhat godot-debugging does
This skill gives an agent practical guidance for reading Godot parser and runtime errors, scene-tree failures, signal problems, and resource-loading issues. It covers causes such as missing node paths, null references, invalid array indexes, duplicate signal connections, and changes made while physics queries are being processed.
The skill can work with Read, Write, Edit, Glob, Grep, Bash, and mcp__godot__* tools. It directs the agent to inspect project files and suggest GDScript changes. For operations triggered during physics callbacks, its guidance uses deferred calls such as call_deferred; node access is checked before methods or properties are used.
The optional-chaining example is tied to Godot 4.2 and later, so that detail should not be applied to older versions.
What it helps with
- trace a GDScript parser error
- locate the source of a null-node failure
- verify a scene-tree node path
- repair a signal and its callback signature
- guard an array access against an invalid index
Example prompts for the agent
- Inspect the current Godot project and diagnose the GDScript error, then suggest a fix.
- Find why
Node not foundappears for this path and check the related scene files. - Review this signal connection and explain why the callback receives the wrong arguments.
How to install godot-debugging
1Skills CLI (Vercel)
npx skills add Zate/cc-godot --skill godot-debugging -a claude-code2Manually: put the files in place
~/.claude/skills/godot-debugging/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/godot-debugging/
1Skills CLI (Vercel)
npx skills add Zate/cc-godot --skill godot-debugging -a codex2Manually: put the files in place
.agents/skills/godot-debugging/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Zate/cc-godot --skill godot-debugging -a cursor2Manually: put the files in place
.cursor/skills/godot-debugging/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Zate/cc-godot godot-debugging2Manually: put the files in place
.github/skills/godot-debugging/SKILL.md1Skills CLI (Vercel)
npx skills add Zate/cc-godot --skill godot-debugging -a gemini-cli2Platform CLI
gemini skills install https://github.com/Zate/cc-godot --path plugins/gd/skills/godot-debuggingManually: put the files in place
.devin/skills/godot-debugging/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Zate/cc-godot --skill godot-debugging -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about godot-debugging
How do I install godot-debugging in Claude Code?
Run npx skills add Zate/cc-godot --skill godot-debugging -a claude-code, then check ~/.claude/skills/godot-debugging/SKILL.md.
What does godot-debugging do?
It helps an agent diagnose Godot errors and troubleshoot recurring GDScript, scene-tree, signal, and resource problems.
Which Godot version is required for optional chaining?
The skill’s optional-chaining example targets Godot 4.2 and later. Its other guidance covers node checks, signals, arrays, and scene errors.
