gdtoolkit
SolidLint and format GDScript files using gdtoolkit (gdlint + gdformat). Use after writing or modifying .gd files, when asked to check code style, fix lint errors, format code, or set up linting configuration. Also use when gdlint/gdformat errors appear in output and need diagnosis. Does NOT require Godot — runs as a standalone Python tool.
Install
Quality Score: 81/100
Skill Content
Details
- Author
- RandallLiuXin
- Repository
- RandallLiuXin/GodotMaker
- Created
- 5 months ago
- Last Updated
- today
- Language
- Python
- License
- NOASSERTION
Similar Skills
Semantically similar based on skill content — not just same category
godot-gdscript-patterns
Idiomatic GDScript 2.0 for Godot 4 - static typing, the @export, @onready and @tool annotations, node lifecycle callbacks, signals as first-class objects, await, class_name registration, lambdas and typed collections. Use when writing or reviewing .gd files, when porting Godot 3 GDScript, or when deciding between get_node, @onready and dependency injection. Explicitly separates Godot 4 syntax from the Godot 3 forms that look similar and fail.
gdunit-driver
Run gdUnit4 unit tests and parse results into structured output. Use this skill after writing or modifying code to verify correctness via unit tests, when diagnosing test failures, or when writing new test files. Triggers: "run tests", "test fails", "write a test", any gdUnit4/unit test mention. Supports both GDScript (.gd) and C# (.cs) test files.
godot-clarity
Build, extend, debug, review, and verify Godot 4 projects with GDScript using version-aware scene, resource, input, UI, world, animation, audio, physics, collision, navigation, persistence, networking, rendering, performance, and export workflows. Use when a task involves project.godot, .gd, .tscn, .tres, nodes, signals, InputMap, TileMapLayer, Camera, CharacterBody, RigidBody, Area, collision shapes/layers/masks, or when creating a playable Godot project or diagnosing engine behavior.