troubleshootinglisted

Use this skill when debugging a specific failure, investigating an incident, analyzing error logs, or diagnosing connectivity problems on the project's platform. Don't use it for proactive instrumentation (use monitoring or observability), writing tests (use testing), CI pipeline config (use deployment), or staging-environment-specific pod debugging (use the staging operations skill).
atretyak1985/swarmery · ★ 3 · Testing & QA · score 62

Install: claude install-skill atretyak1985/swarmery

# Purpose Diagnose and resolve operational issues on the project's platform (see the consumer project's `CLAUDE.md` and `.claude/project.json` → `domainTerms.product` for what the platform is). Covers device connectivity, telemetry streaming, database migrations, image pull failures, performance degradation, and CI/CD deploy-path failures. Provides structured incident response with severity classification and postmortem documentation. **Placeholders used below:** `<mainApp>` = `project.json → mainApp`, `<device>` = `project.json → device` (the device/edge service, if the project has one), `<envAlias>` = `project.json → cloud.envAlias` (the staging environment alias used in slash-command names). **Write tool scope:** Write is used only for creating postmortem documents and diagnostic reports. Never use Write to modify source code, deployment values, or manifests during an incident. # When to use - User reports an issue: "devices not connecting," "telemetry not showing," "deploy failed." - User asks to "debug," "investigate," "diagnose," or "fix" an operational problem. - CI pipeline has failed and user needs root cause analysis. - User asks to "analyze logs" for any of the project's services. - An incident is in progress and triage/resolution is needed. **Disambiguation -- troubleshooting vs monitoring vs observability:** This skill is for reactive debugging of a specific failure. For proactive instrumentation (adding metrics, logging, tracing), use `monitoring` or `obse