Claude-skill-registry GDScript Validate
Validate GDScript changes by refreshing Godot cache and checking diagnostics. Use after creating or editing GDScript files.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/gdscript-validate" ~/.claude/skills/majiayu000-claude-skill-registry-gdscript-validate && rm -rf "$T"
manifest:
skills/data/gdscript-validate/SKILL.mdsource content
GDScript Validate
Validate GDScript file changes by refreshing Godot's language server cache and checking for errors/warnings.
When to Use
After creating or editing GDScript files (
.gd):
- Multiple files: Run once after editing all files
- Single file: Run immediately after editing
Validation Steps
Step 1: Refresh Godot Cache
<this skill dir>/scripts/refresh_godot_lsp.sh
- Updates Godot's language server cache to recognize GDScript changes.
- Important: When processing multiple files, run this once after editing all files (not per file).
Step 2: Check Diagnostics
For specific file:
mcp__ide__getDiagnostics --uri file:///absolute/path/to/file.gd
For entire project:
mcp__ide__getDiagnostics
Note: Only available when IDE MCP server is connected. Skip if unavailable.
Step 3: Review Results
Check the diagnostic output for:
- Errors: Blocking issues that must be fixed
- Warnings: Code quality issues that should be addressed
Note on diagnostic errors:
- Real errors (UNUSED_PARAMETER, TYPE_MISMATCH, etc.): Fix your code
- False positives: If code is correct but error shows "wrong argument count" after changing signatures, ignore it (VSCode LSP cache issue, resolves on restart)
- DO NOT EDIT "./godot/" directory