← ClaudeAtlas

debroid-cli-debuggerlisted

Orchestrate headless Android debugging via JDWP. ACTIVATE this skill whenever asked to debug an Android application, set line or exception breakpoints, inspect runtime variables or Jetpack Compose state, step through execution, evaluate live expressions, watch fields, or diagnose runtime crashes.
PatilShreyas/debroid · ★ 278 · Code & Development · score 89
Install: claude install-skill PatilShreyas/debroid
# Debroid CLI Debugger Skill This skill provides mandatory instructions for AI agents to use the `debroid` CLI for headless Android debugging. **Follow these instructions strictly to avoid context window bloat and execution errors.** ## 🎯 Trigger Conditions Activate this skill whenever the user or task involves: - Debugging an Android application or process live - Setting line breakpoints in Kotlin or Java source files (`debroid break`) - Catching uncaught or caught runtime exceptions (`debroid catch-exception`) - Inspecting live variables, object memory, or Jetpack Compose state (`debroid locals`, `pause-state`, `inspect`) - Stepping through Kotlin/Java code execution (`debroid step`) - Monitoring field access or modifications with watchpoints (`debroid watch`) - Evaluating expressions or mutating variable values in runtime memory (`debroid eval`, `set-var`) ## ⚠️ Critical Agent Rules (DO NOT IGNORE) 1. **Always use `--with-stacktrace`** when polling to get immediate context. 2. **Never poll in an infinite loop**. Poll once or twice, and if the app hasn't hit a breakpoint, instruct the user to interact with the app. 3. **Parse JSON outputs carefully**. All CLI outputs are JSON strings. Extract `sessionId`, `threadId`, `objectId`, `breakpointId`, `exceptionBreakpointId`, `watchpointId`, and `continuationId` **exactly as provided** and reuse them verbatim in subsequent commands. Do not synthesize IDs. 4. **Track trap IDs and remove them when done**. Every `break`, `catch-e