Map production and staging symptoms to data sources and log queries.
npx skills add https://github.com/jonmumm/skills --skill debug-runbook
Please help me install this Agent Skill. Skill: debug-runbook Source: https://github.com/jonmumm/skills/tree/main/debug-runbook Command: npx skills add https://github.com/jonmumm/skills --skill debug-runbook
Structured debugging for production and staging issues requires a disciplined, symptom-driven approach to quickly identify root causes and shorten MTTR.
Tail the deployed worker to reproduce the issue and reference the symptom map to guide your investigation.
High-intent search queries and answers about installing and using this skill.
Debug production issues by starting from user-visible symptoms and mapping them to data sources like Sentry, PostHog, and wrangler logs to assemble evidence and identify root causes. A symptom-map reference guides the investigation steps.
Symptom-driven debugging is a structured approach that traces user-visible symptoms back through system boundaries to data sources and tools. It rapidly identifies root causes in production and staging environments to shorten mean time to resolution.
Troubleshoot staging issues by tailing the deployed worker to reproduce the problem, then referencing the symptom map to select appropriate data sources and log queries for investigation. This workflow ensures disciplined evidence gathering.
You need configured data sources like Sentry and PostHog, access to wrangler and logs, and a symptom-map reference to guide investigation. Checking configuration prerequisites and common pitfalls beforehand ensures reliable debugging sessions.
The best way to investigate mobile app production issues is using a symptom-first workflow that maps user-visible symptoms to appropriate data sources and log queries. This structured approach rapidly identifies root causes across web services and mobile apps.
Debugging workflows fail when they lack a structured symptom-map reference or misconfigure data sources like Sentry and PostHog. Checking configuration prerequisites and common pitfalls ensures reliable evidence assembly for edge worker troubleshooting.
HillBombCreationsAnalyzes growth metrics from GA4, PostHog, MongoDB, and Sentry to generate recommendations.
yumayoDiagnose software defects by analyzing symptoms and investigating the codebase.
diet103Integrate Sentry v8 error tracking and performance monitoring into project services.
jossteiCoordinate specialist debugger agents through a structured five-step evidence-gathering workflow.
