incident-response
Assess production incidents and recommend rollback decisions. Analyze error rates, latency, and resource metrics to determine severity and next steps. Trigger with "should we roll back", "production incident", "service is down", or "error rate spike".
来源信息
- 仓库
- clawpod-app/awesome-openclaw-agent-packs
- 最近来源活动
- 2026年3月31日 03:24
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 46
- 分支
- 11
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- incident-response
- description
- Assess production incidents and recommend rollback decisions. Analyze error rates, latency, and resource metrics to determine severity and next steps. Trigger with "should we roll back", "production incident", "service is down", or "error rate spike".
# Incident Response
Assess production incidents and provide structured rollback recommendations.
## When to Use
- Production service shows elevated error rates or latency
- User reports a customer-facing issue after a deploy
- Monitoring alerts fire for a deployed service
## Steps
1. Identify the affected service and recent deployment history
2. Gather current metrics: error rate, latency (P50/P95/P99), CPU, memory
3. Compare against pre-deploy baseline metrics
4. Assess severity using threshold analysis
5. Recommend: no action / monitor / rollback with clear reasoning
## Output Format
```markdown
## Incident Assessment -- [Service]
**Trigger**: [What happened]
**Last Deploy**: [time] by [author] -- commit [sha]
### Current Metrics vs Baseline
| Metric | Current | Baseline | Delta | Status |
|--------|---------|----------|-------|--------|
| Error Rate | X% | Y% | +Z% | OK/WARN/CRITICAL |
| P99 Latency | Xms | Yms | +Zms | OK/WARN/CRITICAL |
### Recommendation
[Rollback / Monitor / No action needed] -- [reasoning]
### If Rollback Needed
1. [Step-by-step rollback procedure]
2. [Verification steps]
```
在 GitHub 查看