incident-debugging
/incident-debugging
Diagnose a live or recent software failure using logs, traces, metrics, deployment history, and reproduction evidence. Use when service behavior is degraded or an urgent defect affects users.
- Author
- helx0071 ↗
- Repository
- skillsmo ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Diagnose a live or recent software failure using logs, traces, metrics, deployment history, and reproduction evidence. Use when service behavior is degraded or an urgent defect affects users.
Original author description
Diagnose a live or recent software failure using logs, traces, metrics, deployment history, and reproduction evidence. Use when service behavior is degraded or an urgent defect affects users.
How it works
- Goal
- Workflow
- Decision rules
- Boundaries
- Completion standard
- Further reading
SKILL.md preview
--- name: incident-debugging description: "Diagnose a live or recent software failure using logs, traces, metrics, deployment history, and reproduction evidence. Use when service behavior is degraded or an urgent defect affects users." --- # Incident debugging ## Goal Restore safe service while preserving evidence and separating mitigation from root-cause work. ## Workflow 1. Establish user impact, affected systems, start time, severity, current mitigations, and the incident owner's authority. 2. Gather read-only evidence from logs, metrics, traces, health checks, recent releases, and known dependencies; preserve timestamps and correlation identifiers safely. 3. Form competing hypotheses and test the lowest-risk, highest-information checks first. 4. Mitigate only within authorization; verify recovery against user-facing signals and monitor for recurrence. 5. Record timeline, evidence, actions, root cause confidence, unresolved questions, and follow-up owners after stabilization. ## Decision rules - Prioritize reversible mitigation that reduces user harm; distinguish rollback from permanent correction. - If evidence is insufficient, state uncertainty and keep gathering rather than guessing. - Escalate when impact expands, data integrity is threatened, or authority is unclear. ## Boundaries - Do not expose secrets or sensitive user data in logs or summaries. - Do not make destructive production changes, restart services, or change traffic without explicit authority. ## Completion standard Return the requested artifact or findings with enough evidence for a reviewer to understand what changed, what was checked, and what remains uncertain. Distinguish observed facts, inferred risks, and unverified assumptions. Keep the scope tied to the user's request. ## Further reading - [Field guide](references/field-guide.md) — use for task-specific review questions and edge cases. - [Source and rights notes](references/source-notes.md) — use when maintaining this package or reviewing its provenance.
Files in this package (3)
- SKILL.md 2 KB
- references/field-guide.md 1 KB
- references/source-notes.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · helx0071/skillsmo | 90 | MIT |
| evolplus/talos | 90 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version be5931d5409c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100incident-response
Guides production incident handling - assess severity, mitigate first (roll back, disable a flag, scale, fail over), then diagnose from recent changes, metrics, logs and traces, keep a timestamped timeline, draft status updates, and write a blameless postmortem with owned action… - 100incident-investigation-using-metrics-logs-traces
Guides correlating Prometheus metrics, log queries, and distributed traces together during a live incident investigation — using each signal's strengths to narrow from "something is wrong" to a specific root cause faster than any single signal alone. Use when a user asks to… - 90remote-debugging
Diagnose a reported application failure on explicitly authorized remote hosts using bounded logs and runtime evidence. Use when local behavior differs from a known server or deployment; start read-only and keep diagnosis separate from disruptive remediation. - 90incident-response
Runs a live production incident (mitigate, communicate, diagnose, resolve) then a blameless postmortem with timeline and 5 Whys. Use for \"production is down/degraded\", sev1/sev2, users affected now, or writing an RCA. - 84investigate-incident
Investigate production incidents using Datadog. Use when user says "what's causing this alert", "investigate production incident", "root cause analysis for production error", "debug production issue", "what caused this outage", "analyze production logs", "triage production… - 100incident-response-and-change-management
Manage production incidents, emergency changes, rollout freezes, recovery decisions, incident timelines, blameless postmortems, and corrective-action closure. Use when a service is degraded, a deployment or infrastructure change fails, an urgent change is requested, or an…