android-runtime-investigation

What problem does it solve?

This Skill helps you identify the true cause of Android runtime bugs when symptoms vary by emulator, app flavor, and data/network state.

Core Features & Use Cases

• Evidence-first investigation workflow for runtime regressions, prioritizing debugger logs and request/response evidence before code changes.
• Emulator targeting and deterministic repro using Argent to capture UI baselines, reproduce the failing flow, and collect component-tree details at failure points.
• Network and traffic correlation across JS network logs and optional native network logs to confirm contract/serialization/payload shape issues.
• Optional Chucker SQLite inspection via provided scripts to export and query captured traffic from the app sandbox on debuggable builds, then correlate findings with failing screens/endpoints.
• Root-cause summary output that ties the smallest likely fix to specific evidence sources.

Quick Start

Ask: "Investigate a runtime regression on my Android emulator for AniTrend, using Argent debugger logs and network evidence, and provide a root-cause summary tied to the failing screen."