What problem does it solve? Diagnosing runtime issues in Android code often requires guessing where a failure occurs. This Skill instruments a suspected call chain with structured trace logs, captures runtime evidence via logcat, analyzes the results, and removes all instrumentation afterward. ## Core Features & Use Cases - Call Chain Discovery: Uses CodeGraph to explore the call chain from a given entry point before instrumenting. - Structured Trace Logging: Detects the project's logging framework (Timber, android.util.Log, or custom utilities) and applies a consistent trace-logging contract with entry, exit, key-state, and exception logs. - Guided Log Analysis: Provides adb logcat filter commands and analyzes captured logs for sequence, timing, thread, state, and lifecycle issues. - Use Case: When a button click intermittently fails to trigger a network request, invoke /opsx:trace-log with the click handler as the entry point, capture logs during reproduction, and pinpoint where the flow breaks. ## Quick Start Run the slash command /opsx:trace-log followed by the entry point or suspected flow you want to diagnose, then follow the guided instrumentation and log-capture steps.
