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
- 3 months ago
- Last Updated
- today
- Language
- Python
- License
- NOASSERTION
Similar Skills
Semantically similar based on skill content — not just same category
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.
glic-check
Systematic quality check for code, skills, configs, and documents. Two modes — GLIC for internal quality (4 dimensions: Grammar / Logic / Integrity / Containment) and UGLIC adding User Experience (5 dimensions: U + G + L + I + C). Each finding cites file:line; severity is tagged as ERR / WARN / INFO with explicit escalation rules (silent-failure = ERR, 3× repeated WARN → ERR, missing public-param doc = ERR). Use when the user says "GLIC check", "UGLIC check", "do a glic", "systematically review this", "audit my skill", "quality check this code", or any phrasing that asks for a multi-dimension review of code / skills / configs / docs.