What problem does it solve? Android network bugs like intermittent loading failures, token refresh loops, and stale responses overwriting newer UI state are hard to trace because they span transport, auth, parsing, caching, and concurrency layers. This Skill provides a structured workflow to classify the failure type, trace the full request lifecycle, and recommend robust fixes with regression tests. ## Core Features & Use Cases - Failure Classification: Categorizes bugs as connectivity, timeout, TLS, auth, server error, parsing, caching, concurrency, duplicate request, or offline UX issues. - Request Lifecycle Tracing: Inspects the path from trigger point through repository, interceptors, auth refresh, parser, and UI state update, with optional CodeGraph integration for code exploration. - Fix Recommendations & Validation: Suggests patterns like single-flight token refresh, idempotent retries, stale-result protection, and defines tests for airplane mode, slow networks, expired tokens, and out-of-order responses. - Use Case: A user reports that the app shows stale data after a pull-to-refresh on a weak network. Use this Skill to trace the request path, identify a race where an old response overwrites newer state, and get a fix plus regression test plan. ## Quick Start Debug this Android bug where the screen shows outdated data after retrying a failed API request on a slow network.
