debug-screen
Diagnose why the current screen is broken, showing unexpected content, or crashing. Gathers evidence from all layers in parallel and applies a targeted fix.
/rn-dev-agent:debug-screenNo arguments needed. The agent gathers its own evidence from the running app.
Diagnostic Flow
Section titled “Diagnostic Flow”| Step | What happens |
|---|---|
| 1 | Screenshot — capture current screen state immediately |
| 2 | Parallel evidence gathering — simultaneously read error log, console, network log, and component tree |
| 3 | Error type identification — route to the right investigation path (JS error, native crash, data mismatch, navigation issue) |
| 4 | Root cause narrowing — read source files, check store state, inspect native logs |
| 5 | Fix — apply minimal targeted fix, wait for Fast Refresh |
| 6 | Verify recovery — confirm error is gone, re-run the failing action |
When to Use
Section titled “When to Use”- The screen is blank or white with no RedBox
- There is a RedBox or LogBox error showing
- The UI shows wrong data or is in an unexpected state
- The app is frozen or unresponsive
- A network request is failing
- Navigation went to the wrong screen
Just run the command while the broken state is visible on the simulator.