GDScript Validate

Refresh Godot's language server cache and query diagnostics for GDScript files.

21|Updated Jan 24, 2025

Search Tags:#code quality #validation #diagnostics #gdscript #lsp #game dev #godot

Ready to run

npx skills add https://github.com/minami110/godot-signal-extensions --skill gdscript-validate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: GDScript Validate
Source: https://github.com/minami110/godot-signal-extensions/tree/main/.claude/skills/gdscript-validate-skill
Command: npx skills add https://github.com/minami110/godot-signal-extensions --skill gdscript-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the tedious manual work of refreshing Godot's language server cache and checking diagnostics after GDScript changes. It helps you quickly identify and address errors, preventing unnoticed issues from accumulating.

Core Features & Use Cases

Refresh Godot LSP Cache: Automatically updates Godot's language server cache to recognize new or modified GDScript files, ensuring your IDE has the latest project context.
Diagnostic Check: Scans your GDScript project or specific files for errors and warnings, providing immediate feedback on code quality and potential issues.
Use Case: After refactoring a large GDScript class or adding several new script files, run this Skill to instantly update your IDE's understanding of the project and highlight any new issues, saving you from manual restarts or missed errors.

Quick Start

Refresh Godot's language server cache

<this skill dir>/scripts/refresh_godot_lsp.sh

Check diagnostics for the entire project

mcp__ide__getDiagnostics

Frequently Asked Questions about GDScript Validate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate GDScript code quality in Godot projects?▼

GDScript validation identifies errors and warnings by refreshing Godot's language server cache and running diagnostics. After editing or creating files, run refresh_godot_lsp.sh to update the LSP cache, then use mcp__ide__getDiagnostics to scan for issues and receive immediate feedback on code quality.

When should I refresh the Godot language server cache?▼

Refresh the Godot LSP cache after creating new GDScript files or making significant edits to existing scripts. This ensures your IDE recognizes changes and diagnostics reflect the current project state, preventing missed errors from accumulating.

Can I run diagnostics on specific GDScript files or the entire project?▼

Diagnostics can scan either your entire GDScript project or specific files. Use mcp__ide__getDiagnostics to check all files at once or target individual scripts, depending on your refactoring scope.

What's the workflow for identifying GDScript issues after bulk changes?▼

After refactoring multiple GDScript classes or adding several files, execute refresh_godot_lsp.sh to update the language server cache, then run mcp__ide__getDiagnostics to highlight errors and warnings without manual IDE restarts.

What directories or files should I avoid editing when using GDScript validation?▼

Do not edit the ./godot/ directory while validating GDScript. The validation process manages LSP cache updates automatically; manual changes to that directory may interfere with diagnostics accuracy.

Does this validation work with game development workflows in Godot?▼

Yes, GDScript validation integrates with Godot game development workflows. It applies to both single-file edits and multi-file changes across Godot projects, catching issues early in your development cycle.