菜单
Manage and respond to production incidents effectively. Establish on-call rotations, runbooks, and post-mortem processes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Interactive onboarding workflow that interviews users to understand their coding goals and generates PR-ready implementation plans. Use when starting a new development task to ensure clear requirements and structured execution.
Implement security best practices for Gamma integration. Use when securing API keys, implementing access controls, or auditing Gamma security configuration. Trigger with phrases like "gamma security", "gamma API key security", "gamma secure", "gamma credentials", "gamma access control".
Write effective technical documentation including READMEs, API docs, architecture decisions, and inline code documentation.
Build and manage CI/CD pipelines with Azure DevOps. Configure builds, releases, and automate software delivery workflows.
Develop, deploy, and manage Azure Functions for serverless computing. Supports HTTP triggers, timers, queues, and event-driven architectures.
Manage Azure resources effectively using CLI, Portal, Bicep, and ARM templates. Use for provisioning, organizing, and maintaining cloud infrastructure.
| name | incident-response |
| description | Manage and respond to production incidents effectively. Establish on-call rotations, runbooks, and post-mortem processes. |
| triggers | ["/incident","/oncall","/postmortem"] |
This skill covers effective incident response including detection, communication, resolution, and post-incident analysis to minimize downtime and improve reliability.
Use this skill when you need to:
Detection → Triage → Mitigation → Resolution → Post-Incident
↓ ↓ ↓ ↓ ↓
Alerting Assess Stop the Fix root Learn &
System impact bleeding cause improve
Alert Sources
Severity Levels
Initial Assessment
Triage Questions
Communication
Incident #1234 - Payment Service Degraded
Status: Investigating
Severity: SEV 2
Impact: 50% of payment requests failing
Started: 2024-01-15 14:30 UTC
Updates: #incident-1234 (Slack)
Priorities
Mitigation Strategies
Runbook-Driven Response
# Database Connection Pool Exhausted
## Symptoms
- Error: "Too many connections"
- High response times
- Connection timeouts
## Checks
1. Check active connections: `SELECT count(*) FROM pg_stat_activity;`
2. Check connection pool metrics in dashboard
## Mitigation
1. Restart application to reset connection pool
2. Scale up database connection limit temporarily
3. Enable connection pooling (PgBouncer)
## Verification
- Monitor connection count
- Check error rates
- Confirm response times normalizing
Root Cause Analysis
Fix Implementation
Timeline Construction
14:30 - Deployment #5678 to production
14:35 - Error rate alerts triggered
14:40 - Incident declared, rollback initiated
14:45 - Service restored
15:00 - Root cause identified (missing database index)
Post-Mortem Template
# Post-Mortem: Incident #1234
## Summary
Payment service degraded due to missing database index after schema migration.
## Timeline
[Detailed timeline of events]
## Root Cause
Database query performance degraded after adding new column without index.
## Impact
- 50% payment failure rate
- ~$50K revenue impact
- 200 affected customers
## Lessons Learned
- Schema migrations need performance testing
- Missing index detection in CI/CD
## Action Items
| Task | Owner | Due |
|------|-------|-----|
| Add index monitoring | @alice | 2024-01-22 |
| Update migration checklist | @bob | 2024-01-20 |
Blameless Culture
Rotation Design
Handoff Process
Preparation
Incident Management
Automation
See the examples/ directory for:
runbooks/ - Common issue runbookspostmortem-template.md - Post-mortem templateincident-response-playbook.md - Response proceduresoncall-checklist.md - On-call preparation checklist