Skip to content
Skills Library
DevOps & cloud · Analysis

incident-debugging

/incident-debugging

Diagnose incidents in deployed environments from a DevOps operating stance. Use when a staging or production-like service is failing, error rates spike, rollouts regress, infrastructure degrades, or operators need timeline, impact, mitigation, rollback, and routing evidence without mutating systems or exposing secrets by default.

Repository
talos ↗
Licence
Apache-2.0
Last repository change
12.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Diagnose incidents in deployed environments from a DevOps operating stance. Use when a staging or production-like service is failing, error rates spike, rollouts regress, infrastructure degrades, or operators need timeline, impact, mitigation, rollback, and routing evidence without mutating systems or exposing secrets by default.

Original author description

Diagnose incidents in deployed environments from a DevOps operating stance. Use when a staging or production-like service is failing, error rates spike, rollouts regress, infrastructure degrades, or operators need timeline, impact, mitigation, rollback, and routing evidence without mutating systems or exposing secrets by default.

How it works

  1. When to use
  2. Inputs and outputs
  3. Procedure
  4. Hard rules
  5. References
Original SKILL.md headings · 37 lines, 376 words
SKILL.md preview
---
name: incident-debugging
description: Diagnose incidents in deployed environments from a DevOps operating stance. Use when a staging or production-like service is failing, error rates spike, rollouts regress, infrastructure degrades, or operators need timeline, impact, mitigation, rollback, and routing evidence without mutating systems or exposing secrets by default.
agents: [devops]
sdlc_phase: post-release
owner: Platform Eng
status: active
---

# Incident Debugging

## When to use

Use this skill when DevOps is asked to diagnose a deployed-environment incident or regression. The default mode is read-only investigation and mitigation planning; mutation requires explicit operator approval and a scoped task/change record.

## Inputs and outputs

- **Inputs:** incident statement, target environment, time window, recent deploy reports, release version, monitoring/log references, rollback readiness, and any approved access method.
- **Outputs:** incident timeline, impact summary, suspected cause, evidence, immediate mitigation options, rollback recommendation, routing to Dev/SA/QA/PM, and post-incident follow-up tasks.

## Procedure

1. **Declare incident scope.** Record environment, service, version, symptoms, affected users/flows, start time, and current severity. If scope is vague, ask for target environment and symptom.
2. **Stay read-only by default.** Inspect deploy reports, health endpoints, logs, metrics, traces, Kubernetes events, Docker status, and remote host state using approved credential references. Do not mutate services unless explicitly approved.
3. **Build a timeline.** Correlate deploy events, config changes, migrations, alerts, traffic changes, dependency incidents, and first user impact.
4. **Check common failure classes.** Recent release, migration lock/data error, config/secret mismatch, resource exhaustion, dependency outage, certificate/DNS issue, queue backlog, bad rollout, or observability gap.
5. **Assess mitigation.** Options include rollback, disable feature flag, scale capacity, pause worker, drain traffic, retry failed jobs, or route to Dev for code fix. Name risk and owner for each option.
6. **Preserve evidence safely.** Capture sanitized log excerpts, metric names, alert names, resource statuses, and timestamps. Do not include PII, tokens, auth headers, secret values, kubeconfig contents, or private keys.
7. **Route follow-up.** If root cause is code, route to BE/FE Dev. If architecture/data contract, route to SA. If missing test, route to QA-Author/QA-Exec. If unclear product impact, route to PM/BA.
8. **Write incident report content.** Use `docs/devops/<task-id>/incident-debugging.md` or task notes, plus open issues for unresolved risks.

## Hard rules

- Never mutate staging/production during incident debugging without explicit approval and scoped command.
- Never dump secrets or broad environment variables while investigating.
- Never claim root cause without evidence; use confidence labels.
- Never hide an observability gap; record it as a follow-up.
- Never let rollback recommendation omit data/migration compatibility constraints.

## References

- [`../rollback-readiness/SKILL.md`](../rollback-readiness/SKILL.md) - rollback decision support.
- [`../observability-readiness/SKILL.md`](../observability-readiness/SKILL.md) - telemetry gap classification.
- [`../migration-safety/SKILL.md`](../migration-safety/SKILL.md) - migration-related incident checks.

Versions

RepositoryScoreLicence
This page · evolplus/talos90Apache-2.0
helx0071/skillsmo90MIT

Database snapshot: 13.11.2026 · package version 38e17fcf76c7 (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
    Production incidents: outages, 5xx spikes, latency, bad deploys, saturation, expired certs; triage, mitigation, rollback and timeline. Use when a live service is down or degraded, alerts are firing, a deploy just broke something, or a postmortem needs a verified timeline. Not…
  • 100incident-response
    Run a structured Azure incident response workflow for triage, diagnosis, mitigation, and root cause analysis. Use when operations or security teams need guided incident handling for Azure service symptoms.
  • 100cloud-production-ops
    Use when planning or diagnosing production configuration, releases, deployment verification, incidents, rollback, or recovery.
  • 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
    Runs a live production incident: severity, impact, a timestamped timeline, diagnosis, and mitigation options that the user approves one by one; then hands off to /hotfix and /postmortem. Use when the site is down, erroring, slow, leaking data, or payments are failing.
  • 100incident-response
    Incident response and analysis via Harness MCP. Correlate incidents with recent deployments, assess blast radius and downstream service impact, and generate comprehensive postmortem documents. Use when asked to investigate an incident, determine if a deployment caused an issue,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.