What problem does it solve? Native Android failures — a red ./gradlew build, an INSTALL_FAILED_* error, a crash, an ANR, or a device stuck offline — require digging through Gradle output, ADB device state, and logcat buffers by hand. This Skill triages the symptom to the right diagnosis surface and produces an evidence-cited diagnosis instead of guesswork. ## Core Features & Use Cases - Three-surface triage: Routes any symptom to Gradle build-error, ADB device/deploy, or runtime-defect diagnosis, each with documented evidence sources and remedy tables (including an INSTALL_FAILED_* decode table). - Safe evidence collection: Scoped logcat capture, crash-buffer and bugreport analysis, targeted dumpsys, retrace of minified stacks, and Perfetto trace capture — all bounded, PII-redacted, and CLI-first without Android Studio. - Gated fixes with verification: Applies fixes only after explicit approval, then re-verifies with the surface-specific check plus a full ./gradlew build, and never leaves a red state unreported. - Use Case: Your CI emulator run fails with INSTALL_FAILED_UPDATE_INCOMPATIBLE and the app then crashes on launch. The skill decodes the install error, applies the documented uninstall-reinstall remedy, reads the crash buffer for the FATAL EXCEPTION frame, and confirms the fix with a green build. ## Quick Start Ask the assistant to diagnose why ./gradlew build is failing or why the app crashes on your connected Android device, and it will triage the symptom and collect the relevant evidence.
