supabase-incident-runbook
Execute Supabase incident response procedures with triage, mitigation, and postmortem.Use when responding to Supabase-related outages, investigating errors,or running post-incident reviews for Supabase integration failures.Trigger with phrases like "supabase incident", "supabase outage","supabase down", "supabase on-call", "supabase emergency", "supabase broken".
When & Why to Use This Skill
The Supabase Incident Runbook is a specialized Claude skill designed to automate and streamline the incident management lifecycle for Supabase-backed applications. It enables SRE and DevOps teams to perform rapid triage, execute mitigation strategies via kubectl and curl, and generate detailed postmortem reports, significantly reducing Mean Time to Resolution (MTTR) during critical outages.
Use Cases
- Real-time Outage Mitigation: Rapidly diagnose and resolve Supabase service disruptions using automated triage commands and predefined decision trees.
- Database Error Investigation: Debug complex integration failures and connectivity issues by analyzing production cluster logs and system status in real-time.
- Automated Post-Incident Reviews: Streamline the creation of postmortems by automatically collecting evidence and documenting remediation steps taken during an incident.
- On-call Support Assistance: Provide on-call engineers with immediate, actionable runbook procedures and status updates during emergency 'supabase-down' scenarios.
| name | supabase-incident-runbook |
|---|---|
| description | | |
| allowed-tools | Read, Grep, Bash(kubectl:*), Bash(curl:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Supabase Incident Runbook
Prerequisites
- Access to Supabase dashboard and status page
- kubectl access to production cluster
- Prometheus/Grafana access
- Communication channels (Slack, PagerDuty)
Instructions
Step 1: Quick Triage
Run the triage commands to identify the issue source.
Step 2: Follow Decision Tree
Determine if the issue is Supabase-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
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.