unity-investigate-quick

Trace Unity call chains and resolve symbol definitions to explain code behavior.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cuozg/oh-my-unity --skill unity-investigate-quick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-investigate-quick
Source: https://github.com/cuozg/oh-my-unity/tree/main/skills/unity-investigate-quick
Command: npx skills add https://github.com/cuozg/oh-my-unity --skill unity-investigate-quick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly understand Unity codebase behavior by tracing event flows, call chains, and system interactions with minimal tool usage.

Core Features & Use Cases

  • Workflow-driven investigation: parse questions, locate definitions with lsp_goto_definition, trace references with lsp_find_references or grep, and produce a concise summary.
  • Context-aware guidance: load unity-standards when convention context is needed to ensure correct practices.
  • Deterministic replies: output a focused summary plus 1-3 detailed blocks in a tree-like format for quick comprehension.

Quick Start

Explain the call path from a Unity event to its handler, providing a concise flow trace.

Frequently Asked Questions about unity-investigate-quick

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

FAQPage Schema
How do I trace a call chain in a Unity codebase to understand system interactions?

Trace Unity call chains by resolving symbol definitions and following references across the codebase. This workflow parses questions, locates definitions, tracks event flows, and outputs a structured tree-like summary for quick comprehension.

What is the best way to find what calls a specific function in a Unity project?

Find function callers in Unity by using reference tracing to map call chains. The workflow locates definitions, traces references, and outputs a compact summary detailing system interactions and event flows.

How does resolving Unity symbol definitions help with understanding event flows?

Resolving Unity symbol definitions identifies where functions are declared, enabling accurate tracing of event flows from origin to handler. This locates call chain roots and clarifies system interactions.

Can I get a structured summary of Unity code paths without reading the entire codebase?

You can get a structured summary of Unity code paths by parsing questions and tracing references. The workflow outputs a focused summary plus detailed tree-like blocks, minimizing manual codebase reading.

Do I need Unity standards loaded to investigate code paths correctly?

Loading Unity standards is needed when convention context is required to ensure correct practices during investigation. It provides context-aware guidance for tracing call chains and resolving definitions accurately.

What are the limitations of using automated tracing for Unity codebase investigation?

Automated tracing limitations include relying on accurate symbol resolution and reference finding within the Unity codebase. It provides concise summaries but may require manual verification for complex system interactions.