gdscript-linter

Lint GDScript files for syntax errors and style violations.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/Jorge-D-Robles/vibe-rpg --skill gdscript-linter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gdscript-linter
Source: https://github.com/Jorge-D-Robles/vibe-rpg/tree/main/.gemini/skills/gdscript-linter
Command: npx skills add https://github.com/Jorge-D-Robles/vibe-rpg --skill gdscript-linter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Check GDScript code for syntax errors and style violations before running the game, preventing runtime issues and debugging backlogs.

Core Features & Use Cases

  • Lints GDScript files using gdlint (from gdtoolkit) or Godot CLI for on-the-fly validation.
  • Reports line numbers and error descriptions to speed up fixes.
  • Works with the lint.sh workflow to integrate into development and CI pipelines.

Quick Start

Run the lint.sh script against a GDScript file to validate syntax and style before execution.

Frequently Asked Questions about gdscript-linter

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

FAQPage Schema
How do I check GDScript code for syntax errors before running my Godot game?

You can lint GDScript code to identify syntax errors and style violations using gdlint or Godot CLI. This validation process reports line numbers and error descriptions to help fix issues before runtime execution.

Can I integrate GDScript linting into my development and CI pipelines?

Yes, GDScript linting integrates into development and CI pipelines via the lint.sh script. Running this script against target files automates code quality checks and validates syntax during code reviews or pre-run stages.

Do I need gdtoolkit or Godot CLI installed to lint GDScript files?

Yes, you need either gdtoolkit's gdlint or Godot CLI available in your PATH. The linter relies on these external tools to analyze GDScript files and report line numbers with error descriptions for style and syntax validation.

What is the best way to find style violations in my Godot project scripts?

Linting GDScript files is the best way to find style violations quickly. By running the lint.sh workflow against your Godot project scripts, you receive detailed line numbers and error descriptions to speed up fixes.

Why does my GDScript code fail to run without showing any syntax errors?

Hidden style violations or syntax issues in GDScript code can cause runtime failures. Running a static linter analyzes the target file before execution, revealing line numbers and error descriptions to prevent debugging backlogs.

What limitations exist when using a static analysis linter for GDScript?

Static analysis linters for GDScript catch syntax and style violations but cannot detect runtime logic errors. They require gdlint or Godot CLI in PATH and analyze files pre-run, meaning dynamic game state issues remain undetected.