What problem does it solve? When an application hangs, fails silently, or stops responding, developers often guess at causes or dig through logs randomly. This Skill enforces a systematic triage order—runtime logs, workflow status, browser verification, then deployment checks—so root causes are found faster and every step is reported to the user. ## Core Features & Use Cases - Structured Triage Order: Checks runtime logs first, then workflow/background job status, then browser state via screenshots and console inspection, and finally deployment and environment configuration. - Reporting Contract: Requires announcing each check, sharing the evidence found, and explaining the next step so users are never left in silence during debugging. - Common Hang Cause Detection: Looks for missing awaits, unresolved promises, infinite loops, missing environment variables, connection pool exhaustion, and middleware that never returns. - Use Case: A user reports their Vercel deployment shows a blank page. The Skill checks vercel logs, finds a timeout on a database call, inspects the workflow run stuck in running state, and identifies a missing await as the root cause. ## Quick Start Ask the assistant to investigate why your app is stuck or not responding and have it check the logs, workflow runs, and deployment status step by step.
