What problem does it solve? Android developers drowning in crash reports from Crashlytics, Sentry, or Play Console often can't tell whether a crash is a real code defect, an OEM quirk, a known library bug, or a recent regression. This Skill provides a structured triage process that classifies each crash and recommends the right action, so you stop wasting time debugging crashes that need a workaround instead of a fix. ## Core Features & Use Cases - Seven-bucket classification: Sorts crashes into recent regression, OEM/device-specific, known library issue, process death, lifecycle/coroutine misuse, background execution restrictions, or real defect. - Action recommendations: For each crash, decides between Fix, Workaround, Watch, Won't fix, or Escalate, with a fix sketch when applicable. - Prioritization across a backlog: When triaging multiple crashes, sorts by frequency times user impact and highlights the top 2-3 to tackle first. - Use Case: You paste a deobfuscated stack trace showing an IllegalStateException from a Fragment on resume. The Skill identifies it as a process-death/restoration issue and recommends restoring state via SavedStateHandle rather than chasing a phantom null pointer. ## Quick Start Paste a stack trace and ask the assistant to triage this Android crash and tell me whether it needs a fix, a workaround, or escalation.
