AgentSkillsCN

windsurf-incident-runbook

按照分类、缓解与事后分析的流程，执行 Windsurf 事件响应程序。 在应对 Windsurf 相关的停机事件、调查错误，或就 Windsurf 集成失败展开事后复盘时使用。 可使用诸如“Windsurf 事件”、“Windsurf 停机”、“Windsurf 下线”、“Windsurf 值班”、“Windsurf 紧急情况”、“Windsurf 故障”等短语来触发相关操作。

SKILL.md
--- frontmatter
name: windsurf-incident-runbook
description: |
  Execute Windsurf incident response procedures with triage, mitigation, and postmortem.
  Use when responding to Windsurf-related outages, investigating errors,
  or running post-incident reviews for Windsurf integration failures.
  Trigger with phrases like "windsurf incident", "windsurf outage",
  "windsurf down", "windsurf on-call", "windsurf emergency", "windsurf broken".
allowed-tools: Read, Grep, Bash(kubectl:*), Bash(curl:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>

Windsurf Incident Runbook

Overview

Rapid incident response procedures for Windsurf-related outages.

Prerequisites

  • •Access to Windsurf dashboard and status page
  • •kubectl access to production cluster
  • •Prometheus/Grafana access
  • •Communication channels (Slack, PagerDuty)

Severity Levels

LevelDefinitionResponse TimeExamples
P1Complete outage< 15 minWindsurf API unreachable
P2Degraded service< 1 hourHigh latency, partial failures
P3Minor impact< 4 hoursWebhook delays, non-critical errors
P4No user impactNext business dayMonitoring gaps

Quick Triage

bash
# 1. Check Windsurf status
curl -s https://status.windsurf.com | jq

# 2. Check our integration health
curl -s https://api.yourapp.com/health | jq '.services.windsurf'

# 3. Check error rate (last 5 min)
curl -s localhost:9090/api/v1/query?query=rate(windsurf_errors_total[5m])

# 4. Recent error logs
kubectl logs -l app=windsurf-integration --since=5m | grep -i error | tail -20

Decision Tree

code
Windsurf API returning errors?
├─ YES: Is status.windsurf.com showing incident?
│   ├─ YES → Wait for Windsurf to resolve. Enable fallback.
│   └─ NO → Our integration issue. Check credentials, config.
└─ NO: Is our service healthy?
    ├─ YES → Likely resolved or intermittent. Monitor.
    └─ NO → Our infrastructure issue. Check pods, memory, network.

Immediate Actions by Error Type

401/403 - Authentication

bash
# Verify API key is set
kubectl get secret windsurf-secrets -o jsonpath='{.data.api-key}' | base64 -d

# Check if key was rotated
# → Verify in Windsurf dashboard

# Remediation: Update secret and restart pods
kubectl create secret generic windsurf-secrets --from-literal=api-key=NEW_KEY --dry-run=client -o yaml | kubectl apply -f -
kubectl rollout restart deployment/windsurf-integration

429 - Rate Limited

bash
# Check rate limit headers
curl -v https://api.windsurf.com 2>&1 | grep -i rate

# Enable request queuing
kubectl set env deployment/windsurf-integration RATE_LIMIT_MODE=queue

# Long-term: Contact Windsurf for limit increase

500/503 - Windsurf Errors

bash
# Enable graceful degradation
kubectl set env deployment/windsurf-integration WINDSURF_FALLBACK=true

# Notify users of degraded service
# Update status page

# Monitor Windsurf status for resolution

Communication Templates

Internal (Slack)

code
🔴 P1 INCIDENT: Windsurf Integration
Status: INVESTIGATING
Impact: [Describe user impact]
Current action: [What you're doing]
Next update: [Time]
Incident commander: @[name]

External (Status Page)

code
Windsurf Integration Issue

We're experiencing issues with our Windsurf integration.
Some users may experience [specific impact].

We're actively investigating and will provide updates.

Last updated: [timestamp]

Post-Incident

Evidence Collection

bash
# Generate debug bundle
./scripts/windsurf-debug-bundle.sh

# Export relevant logs
kubectl logs -l app=windsurf-integration --since=1h > incident-logs.txt

# Capture metrics
curl "localhost:9090/api/v1/query_range?query=windsurf_errors_total&start=2h" > metrics.json

Postmortem Template

markdown
## Incident: Windsurf [Error Type]
**Date:** YYYY-MM-DD
**Duration:** X hours Y minutes
**Severity:** P[1-4]

### Summary
[1-2 sentence description]

### Timeline
- HH:MM - [Event]
- HH:MM - [Event]

### Root Cause
[Technical explanation]

### Impact
- Users affected: N
- Revenue impact: $X

### Action Items
- [ ] [Preventive measure] - Owner - Due date

Instructions

Step 1: Quick Triage

Run the triage commands to identify the issue source.

Step 2: Follow Decision Tree

Determine if the issue is Windsurf-side or internal.

Step 3: Execute Immediate Actions

Apply the appropriate remediation for the error type.

Step 4: Communicate Status

Update internal and external stakeholders.

Output

  • •Issue identified and categorized
  • •Remediation applied
  • •Stakeholders notified
  • •Evidence collected for postmortem

Error Handling

IssueCauseSolution
Can't reach status pageNetwork issueUse mobile or VPN
kubectl failsAuth expiredRe-authenticate
Metrics unavailablePrometheus downCheck backup metrics
Secret rotation failsPermission deniedEscalate to admin

Examples

One-Line Health Check

bash
curl -sf https://api.yourapp.com/health | jq '.services.windsurf.status' || echo "UNHEALTHY"

Resources

Next Steps

For data handling, see windsurf-data-handling.