What problem does it solve? Debugging Android and Kotlin Multiplatform apps requires platform-specific evidence gathering that generic debugging workflows don't cover — obfuscated release stack traces, ANR traces, memory leaks, Gradle build failures, and Compose recomposition bugs each need dedicated tooling and interpretation. ## Core Features & Use Cases - Crash and ANR investigation: Stream filtered Logcat output, pull ANR traces from the device, and read full Caused by: chains to find root causes. - Release build decoding: Retrace obfuscated R8/ProGuard stack traces with mapping files and inspect keep-rule effects via usage and seeds reports. - Performance and memory analysis: Capture Perfetto traces for SQL-based bottleneck queries, dump heaps for leak analysis, and inspect Compose recomposition with Layout Inspector or android layout --diff. - Use Case: A release build crashes only in production with an obfuscated stack trace — use the retrace workflow with the archived mapping file to decode it, then instrument the implicated layer with a unique per-session log tag to confirm the root cause. ## Quick Start Use the android-debugging skill to investigate why my app crashes on launch by pulling the Logcat output for my package and reading the full stack trace.
