ReddRadar
Agent skill
uloop-get-hierarchy
Get Unity scene hierarchy as a structured tree. Use when you need to: (1) Inspect scene structure and parent-child relationships, (2) Explore GameObjects and their components, (3) Get hierarchy from a specific root path or selected objects. Returns the scene's GameObject tree.
Install this agent skill to your Project
npx add-skill https://github.com/hatayama/unity-cli-loop/tree/main/.claude/skills/uloop-get-hierarchy
SKILL.md
uloop get-hierarchy
Get Unity Hierarchy structure.
Usage
uloop get-hierarchy [options]
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
--root-path |
string | - | Root GameObject path to start from |
--max-depth |
integer | -1 |
Maximum depth (-1 for unlimited) |
--include-components |
boolean | true |
Include component information |
--include-inactive |
boolean | true |
Include inactive GameObjects |
--include-paths |
boolean | false |
Include full path information |
--use-components-lut |
string | auto |
Use LUT for components (auto, true, false) |
--use-selection |
boolean | false |
Use selected GameObject(s) as root(s). When true, --root-path is ignored. |
Global Options
| Option | Description |
|---|---|
--project-path <path> |
Target a specific Unity project (mutually exclusive with --port) |
-p, --port <port> |
Specify Unity TCP port directly (mutually exclusive with --project-path) |
Examples
# Get entire hierarchy
uloop get-hierarchy
# Get hierarchy from specific root
uloop get-hierarchy --root-path "Canvas/UI"
# Limit depth
uloop get-hierarchy --max-depth 2
# Without components
uloop get-hierarchy --include-components false
# Get hierarchy from currently selected GameObjects
uloop get-hierarchy --use-selection
Output
Returns JSON with hierarchical structure of GameObjects and their components.
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?