supabase-incident-runbook
执行Supabase事件响应程序,包括分类、缓解和事后总结。在响应与Supabase相关的故障、调查错误或进行Supabase集成故障的事后审查时使用。通过如“supabase事件”、“supabase故障”、“supabase宕机”、“supabase值班”、“supabase紧急”、“supabase损坏”等短语触发。
📖 中文导读:执行Supabase事件响应程序,包括分类、缓解和事后总结。在响应与Supabase相关的故障、调查错误或进行Supabase集成故障的事后审查时使用。通过如“supabase事件”、“supabase故障”、“supabase宕机”、“supabase值班”、“supabase紧急”、“supabase损坏”等短语触发。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: supabase-incident-runbook description: | 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". 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.