ReddRadar
Agent skill
find-orphaned-meta
Find and clean up orphaned .meta files in a Unity project. Use when you need to: (1) Find .meta files whose corresponding file or folder no longer exists, (2) Clean up Unity warnings about missing assets caused by stale .meta files, (3) Audit .meta hygiene after git operations like branch switches, merges, or file deletions. Also use proactively after deleting files or folders in a Unity project.
Install this agent skill to your Project
npx add-skill https://github.com/hatayama/unity-cli-loop/tree/main/.claude/skills/find-orphaned-meta
SKILL.md
Task
Find orphaned .meta files in the Unity project: $ARGUMENTS
What
Detect .meta files in Assets/ and Packages/ whose corresponding file or folder no longer exists. Unity generates a .meta file for every asset — when the asset is deleted but the .meta remains, Unity logs warnings and the stale .meta pollutes the repository.
When
Use when you need to:
- Find
.metafiles left behind after file/folder deletions - Diagnose Unity warnings like "A meta data file (.meta) exists but its folder/asset can't be found"
- Clean up after git operations (branch switch, merge, rebase) that may leave orphaned
.metafiles
How
Step 1: Run the detection script
.claude/skills/find-orphaned-meta/scripts/find-orphaned-meta.sh
The script scans Assets/ and Packages/ by default. Pass directory arguments to scan specific paths.
Output: one orphaned .meta path per line. Empty output means no orphans found.
Step 2: Report findings
- If no orphans: report "No orphaned .meta files found."
- If orphans found: list them and ask the user whether to delete them.
Step 3: Delete (with user confirmation)
After user approves, delete the orphaned .meta files:
rm -- "<orphaned-meta-path>"
Then run uloop compile to verify Unity no longer reports warnings about missing assets.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
hatayama/unity-cli-loop
uloop-simulate-mouse-ui
Simulate mouse click, long-press, and drag on PlayMode UI elements via EventSystem screen coordinates. Use when you need to: (1) Click buttons or interactive UI elements during PlayMode testing, (2) Drag UI elements from one position to another, (3) Hold a drag at a position for inspection before releasing, (4) Long-press UI elements that respond to sustained pointer-down. For game logic that reads Input System (e.g. WasPressedThisFrame), use simulate-mouse-input instead.
hatayama/unity-cli-loop
uloop-execute-menu-item
Execute Unity Editor menu commands programmatically. Use when you need to: (1) Trigger menu commands like save, build, or refresh, (2) Automate editor actions via menu paths, (3) Run custom menu items defined in project scripts.
hatayama/unity-cli-loop
uloop-find-game-objects
Find GameObjects in the active scene by various criteria. Use when you need to: (1) Search for objects by name, regex, or path, (2) Find objects with specific components, tags, or layers, (3) Get currently selected GameObjects in Unity Editor. Returns matching GameObjects with hierarchy paths and components.
hatayama/unity-cli-loop
uloop-simulate-keyboard
Simulate keyboard key input in PlayMode via Input System. Use when you need to: (1) Press game control keys like WASD, Space, or Shift during PlayMode, (2) Hold keys down for continuous movement or actions, (3) Combine multiple held keys for complex input like Shift+W for sprint.
hatayama/unity-cli-loop
uloop-run-tests
Execute Unity Test Runner and get detailed results. Use when you need to: (1) Run EditMode or PlayMode unit tests, (2) Verify code changes pass all tests, (3) Diagnose test failures with error messages and stack traces. Auto-saves NUnit XML results on failure.
hatayama/unity-cli-loop
uloop-control-play-mode
Control Unity Editor play mode (play/stop/pause). Use when you need to: (1) Start play mode to test game behavior, (2) Stop play mode to return to edit mode, (3) Pause play mode for frame-by-frame inspection.
Didn't find tool you were looking for?