GDScript File Manager

Move, rename, or delete GDScript files with their .uid files.

21|Updated Jan 24, 2025
One-click install
npx skills add https://github.com/minami110/godot-signal-extensions --skill gdscript-file-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GDScript File Manager
Source: https://github.com/minami110/godot-signal-extensions/tree/main/.claude/skills/gdscript-file-manager-skill
Command: npx skills add https://github.com/minami110/godot-signal-extensions --skill gdscript-file-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually moving, renaming, or deleting GDScript files in Godot projects can easily break references due to associated .uid files, leading to frustrating errors and project instability. This Skill automates the safe management of these files.

Core Features & Use Cases

  • Atomic File Operations: Ensures .gd and .uid files are always handled together for moves, renames, and deletions, maintaining their critical association.
  • Reference Integrity: Prevents broken links and resource errors by preserving the correct connection between script files and their unique IDs.
  • Use Case: When reorganizing your Godot project structure, use this Skill to safely move a GDScript file to a new folder without worrying about losing its references or breaking your game, allowing you to focus on development, not debugging file paths.

Quick Start

Rename a GDScript file and its .uid

mv scripts/old_name.gd scripts/new_name.gd &&
mv scripts/old_name.gd.uid scripts/new_name.gd.uid

Frequently Asked Questions about GDScript File Manager

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

FAQPage Schema
How do I move GDScript files in Godot without breaking project references?

Move GDScript files by handling both the `.gd` and `.gd.uid` files together as a paired operation. Godot uses `.uid` files to maintain unique identifiers for scripts; moving only the `.gd` file leaves the `.uid` behind, breaking all references. This Skill automates moving both files simultaneously to preserve project integrity.

Why do my Godot project references break when I rename or delete GDScript files?

GDScript files in Godot are paired with invisible `.gd.uid` files that store unique identifiers used throughout your project. Renaming or deleting only the `.gd` file orphans the `.uid`, causing broken links and resource errors. Manage both files together to maintain valid references.

Can I reorganize my Godot project structure without manual .uid file editing?

Yes. Automated paired operations on `.gd` and `.gd.uid` files eliminate the need for manual `.uid` editing during refactoring. This Skill handles moves, renames, and deletions atomically, preserving the critical association between script files and their unique identifiers.

What's the best way to safely delete unused GDScript files from a Godot project?

Delete GDScript files using atomic operations that remove both the `.gd` and `.gd.uid` together. Deleting only the script file leaves orphaned `.uid` files that can cause lingering reference errors. This Skill ensures complete removal and project cleanup.

Does this work when refactoring large Godot projects with many interdependent scripts?

Yes. This Skill is designed for project reorganization workflows where scripts reference each other through Godot's resource system. Atomic paired operations on `.gd` and `.gd.uid` files maintain reference integrity across the entire project during large-scale refactoring.