debug-app

Monitors Metro terminal output to detect and fix runtime errors in React Native mobile apps.

808|167|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/microsoft/power-platform-skills --skill debug-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-app
Source: https://github.com/microsoft/power-platform-skills/tree/main/plugins/mobile-apps/skills/debug-app
Command: npx skills add https://github.com/microsoft/power-platform-skills --skill debug-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running mobile apps often fail silently — empty lists, blank screens, or swallowed network errors that never surface as visible crashes. This Skill watches the Metro dev-server terminal output, classifies runtime and bundle errors, and fixes them autonomously so you do not have to manually read logs and trace data paths.

Core Features & Use Cases

  • Autonomous monitor loop: Polls the Metro terminal every 5 seconds, classifies issues using an 8-category table (JS Runtime, Import/Bundle, Network/API, Native, React, and more), applies one fix at a time, and exits after 3 consecutive clean polls.
  • Symptom-driven diagnostics: Accepts a free-text symptom (e.g., "todos not appearing on home screen"), injects temporary traceable console.log statements at data-path boundaries, reads the terminal output, and cleans up all injected logs after the root cause is fixed.
  • Smart routing: Fixes app screens, hooks, and components inline, but routes Dataverse schema issues to /add-dataverse, auth registration issues to /set-app-registration-native, and connector problems to /add-connector instead of editing generated or native config files.
  • Use Case: After starting your Power Apps mobile app with npm run dev, run /debug-app "list empty after refresh" to have the agent trace the data path from screen to generated service, identify a silent mock-data fallback, and fix it.

Quick Start

Run /debug-app with an optional symptom description after starting your app with npm run dev, for example: /debug-app "login button does nothing".

Frequently Asked Questions about debug-app

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

FAQPage Schema
How do I debug a React Native mobile app running on Metro?

Run /debug-app after starting the app with npm run dev and loading it on a device or simulator. The skill reads the Metro terminal output every 5 seconds, classifies errors into 8 categories, and fixes them one at a time until 3 consecutive clean polls confirm the app is healthy.

How to diagnose silent failures like empty lists in a mobile app?

Pass a free-text symptom such as /debug-app "todos not appearing on home screen". The skill injects temporary console.log statements at data-path boundaries, asks you to reproduce the symptom, reads the trace output from the Metro terminal, and removes all injected logs after fixing the root cause.

Does this debugging approach work with web or browser-based apps?

No. The skill targets only native dev clients on a device or simulator, using the Metro terminal as the sole log source. It explicitly prohibits browser automation, curl, fetch, or direct requests to Metro/localhost endpoints for runtime diagnosis.

Why does the debugger refuse to edit files in src/generated?

Files in src/generated/ are produced by code generation and must not be hand-edited. Instead, the skill fixes the upstream query or schema and runs npm run generate-schemas, or routes you to /add-dataverse or /add-connector when the service stub or datasource is missing.

When does the debug monitoring loop stop running?

The loop exits after 3 consecutive clean poll cycles, when you type stop, or when the 50-cycle iteration cap is reached. In symptom mode, the clean-cycle exit is suspended until the symptom is marked resolved or escalated to unresolved.md.