☁️ DevOps & Cloud · Incidents & Edge Deploys

Run a calm incident response flow

Roles, comms cadence, and mitigation-first mindset that turns chaos into checklist.

intermediate~30 minDevOps EngineersSREsCloud Architects

Steps

1Declare early; assign Incident Commander separate from fixers
2Mitigate first (rollback, feature-flag off), root-cause later
3Post status updates every 30 min even when 'still investigating'
4Log timeline entries with timestamps as decisions happen
5End with customer-facing summary plus internal blameless retro within 48h
6Convert every retro action item into tracked issues with owners

Common Pitfalls

▲Hero debugging without comms, stakeholders blind
▲Retro actions dying in a doc

Commands

Install with skills CLI

$ npx skills add aniruddhaadak80/skills --skill incidents-vercel-incident-response-flow

Install globally

$ npx skills add aniruddhaadak80/skills --skill incidents-vercel-incident-response-flow -g

Tags

#incident-response#sre#devops-cloud#incidents-vercel

Install this skill

$ npx skills add aniruddhaadak80/skills --skill incidents-vercel-incident-response-flow -a opencode

SKILL.md

# Run a calm incident response flow

> Roles, comms cadence, and mitigation-first mindset that turns chaos into checklist.

## When to Use This Skill

Roles, comms cadence, and mitigation-first mindset that turns chaos into checklist.

## Steps

1. Declare early; assign Incident Commander separate from fixers
2. Mitigate first (rollback, feature-flag off), root-cause later
3. Post status updates every 30 min even when 'still investigating'
4. Log timeline entries with timestamps as decisions happen
5. End with customer-facing summary plus internal blameless retro within 48h
6. Convert every retro action item into tracked issues with owners

## Common Pitfalls

- Hero debugging without comms, stakeholders blind
- Retro actions dying in a doc

View source on GitHub ↗

Preview-per-PR, promotion flows, and env hygiene on platforms like Vercel/Netlify.

☁️ DevOps & Cloud·~20m

Open →

Deploy to Vercel with token-based CLI authintermediate

Authenticate Vercel CLI via a stored token instead of browser OAuth — the reliable path when clock drift breaks login flows. Use when deploying, linking project

☁️ DevOps & Cloud·~15m