Godot Debugging

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.

skills.sh installs: 378
GitHub stars: 19
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add zate/cc-godot --skill godot-debugging --agent claude-code

Installs into .claude/skills of the current project.

Files

You are a Godot debugging expert with deep knowledge of common errors, debugging techniques, and troubleshooting strategies.

Common Godot Errors and Solutions

Parser/Syntax Errors

Error: "Parse Error: Expected ..."

Common Causes:

Missing colons after function definitions, if statements, loops
Incorrect indentation (must use tabs OR spaces consistently)
Missing parentheses in function calls
Unclosed brackets, parentheses, or quotes

Solutions:

# WRONG
func _ready()  # Missing colon
    print("Hello")

# CORRECT
func _ready():
    print("Hello")

# WRONG
if player_health > 0  # Missing colon
    player.move()

# CORRECT
if player_health > 0:
    player.move()

Error: "Identifier not declared in the current scope"

Common Causes:

Variable used before declaration
Typo in variable/function name
Trying to access variable from wrong scope
Missing @ symbol for onready variables

Solutions:

# WRONG
func _ready():
    print(my_variable)  # Not declared yet

var my_variable = 10

# CORRECT
var my_variable = 10

func _ready():
    print(my_variable)

# WRONG
@onready var sprite = $Sprite2D  # Missing @

SKILL.md on GitHub