Skip to content
Skills Library
Programming · Automation

gdscript-file-manager

/gdscript-file-manager

Move, rename, or delete GDScript files with their .uid files for Godot projects. Use when reorganizing code, renaming scripts, or removing unused GDScript files.

Licence
MIT
Last repository change
01.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 01.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Move, rename, or delete GDScript files with their .uid files for Godot projects. Use when reorganizing code, renaming scripts, or removing unused GDScript files.

Original author description

Move, rename, or delete GDScript files with their .uid files for Godot projects. Use when reorganizing code, renaming scripts, or removing unused GDScript files.

How it works

  1. Core Principle
  2. Before Any Operation: Check Owners
  3. Operations
  4. Important Notes
Original SKILL.md headings · 71 lines, 289 words
SKILL.md preview
---
name: gdscript-file-manager
description: Move, rename, or delete GDScript files with their .uid files for Godot projects. Use when reorganizing code, renaming scripts, or removing unused GDScript files.
allowed-tools:
  - Bash
---

# GDScript File Manager

Manage GDScript files (.gd) along with their corresponding .uid files.

## Core Principle

Godot Engine auto-generates a `.uid` file for each resource. **Always handle .gd and .uid files together.**

## Before Any Operation: Check Owners

Run **godot-resource-owners** on the target first:

```bash
${CLAUDE_PLUGIN_ROOT}/skills/godot-resource-owners/scripts/owners.sh <project_root> <file>.gd
```

- **Delete**: if any owner is listed, stop — remove or redirect those references first, then delete.
- **Move / Rename**: owners tagged `(uid)` or `(path+uid)` survive the move (Godot re-resolves them by UID). Owners tagged `(path)` — `preload("res://old/path.gd")` literals, `project.godot` autoloads, etc. — will break; update those literals to the new path right after the move.

## Operations

### Move Files

```bash
# 1. Verify destination
ls <destination-dir>

# 2. Move both files
mv <source>.gd <destination>.gd && mv <source>.gd.uid <destination>.gd.uid

# 3. Verify
ls <destination-dir> && ls <source-dir>

# 4. Update every owner tagged (path) to the new res:// path
```

### Rename Files

```bash
# 1. Rename both files
mv <old-name>.gd <new-name>.gd && mv <old-name>.gd.uid <new-name>.gd.uid

# 2. Verify
ls -la <directory>

# 3. Update every owner tagged (path) to the new res:// path
```

### Delete Files

```bash
# 1. Verify target and confirm it has no owners (see above)
ls -la <directory>

# 2. Delete both files
rm <filename>.gd && rm <filename>.gd.uid

# 3. Verify
ls -la <directory>
```

## Important Notes

- Never manually create or edit .uid files - Godot manages them automatically
- Always process both files together to avoid breaking project references
- Verify files before operations using `ls` commands
- `.uid` references survive a move; `res://` path literals in other scripts and in `project.godot` do not — always run the owners check first

See @examples.md for detailed examples and troubleshooting.
Files in this package (2)
  • SKILL.md 2 KB
  • examples.md 1 KB

Versions

The database has no other skills named gdscript-file-manager.

Database snapshot: 13.11.2026 · package version b71f918b2182 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100godot-gdscript-patterns
    Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization. Use when building Godot games, implementing game systems, or learning GDScript best practices.
  • 100godot-gdscript-patterns
    Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization. Use when building Godot games, implementing game systems, or learning GDScript best practices.
  • 100godot-gdscript-patterns
    Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization. Use when building Godot games, implementing game systems, or learning GDScript best practices.
  • 100godot-testing
    Use when writing tests for Godot projects — TDD workflow with GUT and gdUnit4, covers both GDScript and C#
  • 100godot
    Godot 4 work in a project with project.godot, .gd or .tscn files. Use to verify a change in the running game, fix a headless GDScript test run that hangs or exits 0, hand-edit a .tscn, commit .uid files, or catch an invented API.
  • 100godot-testing
    Use when writing tests for Godot projects — TDD workflow with GUT and gdUnit4, covers both GDScript and C#

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.