v-device-debug

Installation
SKILL.md

v-device-debug

You cannot adb into the device. The user is your hands and eyes: they install builds, screenshot failures, and report what they see. Your job is to make every round-trip converge — each build must either fix the bug or reveal the next fact.

When to Use

  • The app runs on a phone/device only the user holds; you have no adb/logcat access.
  • The loop is: user screenshot → you diagnose → remote build → tunnel delivery → user installs → next screenshot.
  • Works alongside any build host (cloud VM, CI, local machine) and any tunnel.

Do NOT use when you have direct device access (just use adb), or for emulator-only work (no user loop needed).

Steps

  1. Read the screenshot literally.
    • Transcribe the exact error text (exception class, message, exit codes, percentages, step names). Quote it back — never paraphrase an error from memory.
    • Note what PASSED around the failure (green checks, completed steps). Passed steps bound the fault: the bug is downstream of everything green.
    • One screenshot = one failure class. Fix that class before theorizing about the next.
Installs
1
First Seen
7 days ago