incident-response
Sev-classified incident loop for SRE — detect, contain, diagnose, communicate, recover.
- License 许可
- Apache-2.0
- 最近更新
- 2026-08-30
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- incident-response
- description
- Sev-classified incident loop for SRE — detect, contain, diagnose, communicate, recover.
03 SKILL.md 正文
Observe before you change anything. Call resolve_service, then observe_health and fetch_logs.
- Name the user-visible symptom and the SLO at risk (FOREX rejects, checkout saga, Shopify HMAC, ticket SLA).
- Bound blast radius to one business unit and its dedicated cluster/account.
- Contain with the smallest reversible action. Prefer rollback or traffic shift over config rewrites.
- Matching-engine reject spikes and Shopify HMAC failures start at Sev2. Do not page CLS/settlement without that context.
page_oncallandrollback_deployrequire approval.- After recovery, write a six-line timeline: detect, contain, cause, fix, verify, follow-up.
Never run host-destructive commands. Never delete Kubernetes namespaces from this harness.
04 同仓库更多 Skills
Use when working with PDF files — reading, extracting text or tables, merging, splitting, or filling forms. Provides correct library choices and common patterns.
code-review
Use when asked to review code, audit a file for bugs, check code quality, or suggest improvements. Provides a structured review process and issue categorisation.
agent-builder
Use when building a new agent harness, designing tool systems, or structuring multi-agent workflows. Provides patterns, templates, and decision trees for harness engineering.
ticket-sla-breach
Support ticket SLA breach
quote-to-order-break
B2B quote-to-order break
payments-decline-storm
Payments decline storm