Diagnose production issues from Sentry URLs, Slack messages, or descriptions.
npx skills add https://github.com/cuemath/dotclaude --skill diagnose-cuemath
Please help me install this Agent Skill. Skill: diagnose Source: https://github.com/cuemath/dotclaude/tree/main/skills/diagnose Command: npx skills add https://github.com/cuemath/dotclaude --skill diagnose-cuemath
This Skill rapidly diagnoses production issues by analyzing Sentry errors, Slack messages, or direct problem descriptions, pinpointing the root cause of infrastructure or application failures.
Diagnose the production issue described in the Sentry URL https://sentry.io/organizations/cuemathcom/issues/1234567890/.
High-intent search queries and answers about installing and using this skill.
To diagnose production issues from a Sentry URL, the system analyzes the link to systematically gather CloudWatch logs, Kubernetes metrics, and database records. It verifies the error claims with real-time production data before presenting a confidence-scored root cause diagnosis.
You can find a root cause by providing a Slack message link or a direct text description of the failure. The tool applies a structured debugging framework to triage the report and verify hypotheses against live infrastructure data.
The best way to debug Kubernetes application failures is verifying claims with real-time production data rather than code analysis alone. This approach gathers metrics from Kubernetes and CloudWatch to formulate and test hypotheses, yielding a data-backed diagnosis.
Root cause analysis works directly with CloudWatch logs and Sentry errors by systematically correlating them during the verification phase. It cross-references these production data sources to confirm the true infrastructure or application failure point.
To troubleshoot production issues from a critical bug report, input the Sentry issue URL or problem description to initiate diagnosis. The system systematically plans, triages, and verifies the issue against live database and log data to provide actionable remediation steps.
sasamukuAnalyze Sentry issues from URLs with root cause and codebase exploration.
netguy204Diagnose stuck orchestrator work units using status checks and log review.
yaacovProvide curated PromQL queries and metric references for OpenShift cluster monitoring.
kevindreeInspect live DOM, console, network, and accessibility data via Chrome DevTools MCP.
