Agent skill

windsurf-incident-runbook

Execute Windsurf incident response when AI features fail or cause production issues. Use when Cascade breaks code, Windsurf service is down, AI-generated code causes production incidents, or team needs emergency Windsurf troubleshooting. Trigger with phrases like "windsurf incident", "windsurf outage", "windsurf broke production", "cascade caused bug", "windsurf emergency". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-coderead-onlyMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill windsurf-incident-runbook --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.11.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadGrepBash(git:*)Bash(curl:*)
Requires: Designed for Claude Code, also compatible with Codex and OpenClaw
Path: skills/.curated/windsurf-incident-runbook/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Windsurf Incident Runbook ## Overview Incident response procedures for Windsurf-related issues: Cascade service outages, AI-generated code causing bugs, and team workflow disruptions. ## Prerequisites - Access to Windsurf dashboard and status page - Git access to affected repositories - Team communication channel (Slack, Teams) ## Severity Levels | Level | Definition | Response Time | Examples | |-------|------------|---------------|----------| | P1 | Production broken by AI code | < 15 min | Cascade-generated code deployed with critical bug | | P2 | Team workflow blocked | < 1 hour | Windsurf service outage, all Cascade down | | P3 | Degraded AI features | < 4 hours | Slow Cascade, Supercomplete intermittent | | P4 | Minor inconvenience | Next business day | Specific model unavailable, feature regression | ## Quick Triage Decision Tree ``` Is Windsurf service itself down? ├─ YES: Check https://status.windsurf.com │ ├─ Status page shows incident → WAIT for Windsurf to resolve │ │ Action: Switch to manual coding, notify team │ └─ Status page green → Local issue │ Action: Restart Windsurf, check internet, re-authenticate │ └─ NO: Did AI-generated code cause a production issue? ├─ Y

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Severity Levels
  4. Quick Triage Decision Tree
  5. P1 Playbook: AI Code Caused Production Bug
  6. Step 1: Immediate Mitigation
  7. Step 2: Identify Root Cause
  8. Step 3: Fix and Validate
  9. P2 Playbook: Windsurf Service Outage
  10. Step 1: Confirm and Communicate
  11. Step 2: Team Notification
  12. Step 3: Workarounds During Outage
  13. P3 Playbook: Degraded AI Features
  14. Post-Incident Actions
Commands it runs
set -euo pipefail
Revert the deployment
git log --oneline -10  # Find the bad commit(s)
If tagged with [cascade]:
git revert HEAD --no-edit  # Revert most recent commit
git push origin main       # Deploy revert
If multiple Cascade commits:
git revert --no-commit HEAD~3..HEAD  # Revert last 3 commits
git commit -m "revert: undo cascade changes causing [issue]"
git push origin main
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the windsurf-incident-runbook skill do?

Execute Windsurf incident response when AI features fail or cause production issues. Use when Cascade breaks code, Windsurf service is down, AI-generated code causes production incidents, or team needs emergency Windsurf troubleshooting. Trigger with phrases like "windsurf incident", "windsurf outage", "windsurf broke production", "cascade caused bug", "windsurf emergency". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill windsurf-incident-runbook --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going