What problem does it solve? Investigating Android crashes from raw logcat output is slow and error-prone: stack traces mix framework noise with app frames, and symptoms often hide the real root cause. This Skill structures crash analysis so you find the actual defect instead of patching symptoms. ## Core Features & Use Cases - Crash Classification: Categorizes exceptions like NullPointerException, IllegalStateException, and fragment transaction crashes into root-cause buckets such as lifecycle state, threading, or stale references. - Suspect Code Location: Walks the stack trace to the first meaningful app frame and inspects callers, lifecycle owners, coroutines, and adapters, optionally grounded by CodeGraph exploration. - Safe Fix Recommendations: Proposes minimal fixes (null handling, lifecycle-aware collection, guarded fragment transactions) with explicit validation steps and regression tests, while flagging anti-patterns like broad try/catch and force unwraps. - Use Case: Given a production NullPointerException logcat trace from a Fragment, the Skill identifies the destroyed view access after onDestroyView, recommends viewLifecycleOwner.lifecycleScope, and lists regression tests to add. ## Quick Start Analyze this Android crash logcat output and tell me the likely root cause, the suspect files, and the safest fix with verification steps.
