android-debugging

Gather Android-specific evidence from Logcat, ADB, and ANR traces during debugging.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/kotlinknight/NutriSoloAndroid --skill android-debugging-kotlinknight
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: android-debugging
Source: https://github.com/kotlinknight/NutriSoloAndroid/tree/main/.agents/skills/android-debugging
Command: npx skills add https://github.com/kotlinknight/NutriSoloAndroid --skill android-debugging-kotlinknight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers debug Android and Kotlin Multiplatform issues by augmenting systematic debugging with Android-specific evidence-gathering techniques such as Logcat, ADB, ANR traces, R8 stack trace decoding, memory-leak analysis, Gradle build failure diagnosis, and Compose recomposition debugging.

Core Features & Use Cases

  • Android-specific evidence gathering: collect and correlate logs from Logcat, ADB, and ANR traces to identify root causes.
  • Memory and stack-trace analysis: decode R8 mappings and analyze memory leaks to prevent regressions.
  • Build and UI debugging guidance: triage Gradle failures and Compose recomposition issues in end-to-end workflows.
  • Use Case: when an app crashes during Kotlin Multiplatform integration, use Android-specific techniques to locate the root cause and verify a fix across platforms.

Quick Start

Reproduce the issue on a connected Android device and follow the Android-specific evidence steps (Logcat, ADB, ANR traces) to gather logs and traces for root-cause analysis.

Frequently Asked Questions about android-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug an Android ANR or crash using Logcat and ADB?▼

Debug an Android ANR or crash by reproducing the issue on a connected device, then systematically gathering and correlating evidence from Logcat, ADB, and ANR traces to pinpoint the root cause.

What is the best way to diagnose memory leaks in a Kotlin Multiplatform module?▼

Diagnose memory leaks in a Kotlin Multiplatform module by applying Android-specific memory-leak analysis techniques during a phased investigation to identify the root cause and verify the fix across platforms.

How do I decode R8 stack traces for an Android app crash?▼

Decode R8 stack traces for an Android app crash by applying R8 mapping analysis alongside Logcat evidence gathering to identify obfuscated root causes and prevent regressions.

Can I use Android debugging techniques to triage Gradle build failures?▼

Yes, you can use Android debugging techniques to triage Gradle build failures by applying systematic evidence-gathering workflows to isolate and resolve build configuration issues.

How do I debug Jetpack Compose recomposition issues?▼

Debug Jetpack Compose recomposition issues by using Compose recomposition debugging techniques within a phased investigation flow to identify performance bottlenecks and root causes.

Does this systematic debugging approach work for Kotlin Multiplatform integration crashes?▼

Yes, this systematic debugging approach works for Kotlin Multiplatform integration crashes by using Android-specific evidence-gathering techniques to locate the root cause and verify fixes across platforms.