ad-catch

Identifies and traps specified Android exceptions, captures frame locals, and generates a root-cause report.

3|Updated May 10, 2026
One-click install
npx skills add https://github.com/Acendas/android-debugger --skill ad-catch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ad-catch
Source: https://github.com/Acendas/android-debugger/tree/main/skills/ad-catch
Command: npx skills add https://github.com/Acendas/android-debugger --skill ad-catch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Debugging Android crashes can be slow and guesswork-based. ad-catch enables authoring a Debug Plan that traps the next exception, captures the frame locals, and produces a structured root-cause report to guide fixes.

Core Features & Use Cases

  • Author a Debug Plan that installs an exception breakpoint, captures the failing frame's locals, grades a hypothesis about why, and resumes. The orchestrator submits the plan, polls progress events, and reads the structured report.
  • Monitor plan progress and iteratively drill down into snapshot data and feel outputs to surface the root-cause.
  • Use interactive drill-down or automated grading to decide next steps without mutating app state.

Quick Start

Attach to the target app, select the exception to catch, and run the ad-catch plan to begin root-cause analysis.

Frequently Asked Questions about ad-catch

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

FAQPage Schema
How do I find the root-cause of an Android exception crash?

To find the root-cause of an Android exception, you can author a Debug Plan that traps the next occurrence, captures the failing frame locals, and generates a structured root-cause report to guide fixes.

Can I capture local variables when an Android breakpoint hits?

Yes, capturing local variables when an Android breakpoint hits is possible by installing an exception breakpoint through a Debug Plan, which harvests the failing frame's locals and feel outputs.

How do I automate Android crash debugging for a specific package?

Automate Android crash debugging for a specific package by applying optional package filters and an exception FQN resolver to narrow targets before launching the debug plan to monitor events.

What is the best way to grade a hypothesis about an Android crash?

The best way to grade a hypothesis about an Android crash is to use interactive drill-down or automated grading on captured snapshot data, allowing you to decide next steps without mutating app state.

Does Android root-cause analysis require mutating the app state?

No, Android root-cause analysis does not require mutating the app state; you can monitor plan progress and iteratively drill down into snapshot data to surface the root-cause safely.

When should I use a debug plan instead of manual Android debugging?

Use a debug plan instead of manual Android debugging when crashes are slow to reproduce and guesswork-based, as it automates trapping the exception and harvesting structured snapshots.