用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/TheBushidoCollective/han --skill incident-response命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Review current branch changes against REVIEW.md guidelines
Use when kotlin coroutines for structured concurrency including suspend functions, coroutine builders, Flow, channels, and patterns for building efficient asynchronous code with cancellation and exception handling.
Use when building modular Angular applications requiring dependency injection with providers, injectors, and services.
基于 SOC 职业分类
| name | incident-response |
| description | Manage incident response workflow with Sentry alerts and issue tracking |
sentry:incident-response - Manage incident response workflow with Sentry alerts and issue tracking
/incident-response [arguments]
Coordinate incident response using Sentry's monitoring and alerting capabilities to quickly identify, triage, and resolve production issues.
This command provides a structured workflow for responding to production incidents detected by Sentry.
/incident-response [incident-type]
User: /incident-response
Claude: Checking Sentry for active incidents...
## Active Incidents Detected: 2
### Incident #1: High Error Rate in Payment Service
- **Severity**: Critical
- **Status**: Ongoing (Started 23 minutes ago)
- **Affected Service**: payment-processor (production)
- **Impact**:
- Error rate: 45% (normal: 0.2%)
- Affected users: ~2,300
- Failed transactions: 1,247
**Primary Issue:**
TypeError: Cannot read property 'amount' of null
- Events: 1,247 (spiking)
- First seen: 23m ago
- Correlated with: v3.2.1 deployment (25m ago)
**Recommended Actions:**
1. Rollback to v3.2.0 immediately
2. Investigate null handling in payment amount processing
3. Enable feature flag to bypass new code path
Would you like me to help with rollback or investigation?
---
### Incident #2: Database Connection Pool Exhaustion
- **Severity**: High
- **Status**: Ongoing (Started 1 hour ago)
- **Affected Service**: api-backend (production)
- **Impact**:
- Slow response time: P95 4,200ms (normal: 800ms)
- Affected users: ~890
- Timeout errors: 234
**Primary Issue:**
Error: Connection pool timeout after 30000ms
- Events: 234 (steady)
- Pattern: Gradual increase over 2 hours
- Possible cause: Connection leak in database queries
**Recommended Actions:**
1. Restart connection pool (temporary fix)
2. Audit for unclosed database connections
3. Increase pool size as immediate mitigation
4. Review recent database query changes
---
## Incident Response Workflow
For Incident #1 (Critical), I recommend:
**Phase 1: Immediate Mitigation (Now)**
1. Execute rollback to v3.2.0
2. Verify error rate returns to normal
3. Enable monitoring for rollback confirmation
**Phase 2: Investigation (Next 30 minutes)**
1. Use Seer AI to analyze root cause in v3.2.1
2. Review code changes affecting payment processing
3. Identify the null value source
**Phase 3: Fix & Deploy (Next 2-4 hours)**
1. Implement null check before amount access
2. Add unit tests for null payment scenarios
3. Deploy fix with gradual rollout
4. Monitor error rates during deployment
**Phase 4: Post-Incident (After resolution)**
1. Document root cause and fix
2. Update runbooks with this incident
3. Add alerts for similar patterns
4. Review deployment checklist
Which incident would you like to focus on first?
This command can help with:
Assess Impact
Find Root Cause
Mitigate
Communicate
Resolve
Learn
incident-type (optional): error-spike, performance-degradation, outage/investigate-errors: Deep dive into specific errors/check-releases: Verify release correlation/analyze-performance: Check performance impact/query-events: Custom investigation queries