What problem does it solve? After implementing features in a Godot project, GDScript code often accumulates loose typing, broad engine types, undocumented methods, and runtime node assembly that should live in scenes. This Skill performs scoped, behavior-preserving hygiene on changed GDScript files and directly related scenes so code stays typed, documented, and maintainable. ## Core Features & Use Cases - Scoped cleanup: Resolves scope from explicit user input or the working diff, touching only changed .gd files, affected interfaces, and directly related .tscn scenes while leaving unrelated legacy debt alone. - Typed interface enforcement: Replaces broad types like Node or Object with concrete project script types, adds explicit local types, typed enums, typed exports, and native ## documentation with supported BBCode. - Scene-authoring checks: Flags runtime construction of stable game objects (via Node.new() or scripted child assembly) that belong in .tscn scenes, asking before any behavioral or architectural change. - Metadata recovery: Refreshes Godot class metadata via headless import when a project type is unresolved, instead of weakening types to evade stale caches. - Use Case: After finishing a Godot feature branch, run this Skill to tighten typing on the changed scripts, document non-obvious method contracts, validate with focused checks, and produce a structured completion report. ## Quick Start Use gdscript-cleanup to clean the GDScript changed by this task and validate the fixes.
