supabase-advanced-troubleshooting
应用Supabase高级调试技术以解决难以诊断的问题。在标准故障排除失败、调查复杂竞争条件或为Supabase支持升级准备证据包时使用。通过短语如“Supabase硬bug”、“Supabase神秘错误”、“Supabase难以调试”、“困难的Supabase问题”、“Supabase深度调试”触发。
📖 中文导读:应用Supabase高级调试技术以解决难以诊断的问题。在标准故障排除失败、调查复杂竞争条件或为Supabase支持升级准备证据包时使用。通过短语如“Supabase硬bug”、“Supabase神秘错误”、“Supabase难以调试”、“困难的Supabase问题”、“Supabase深度调试”触发。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: supabase-advanced-troubleshooting description: | Execute apply Supabase advanced debugging techniques for hard-to-diagnose issues. Use when standard troubleshooting fails, investigating complex race conditions, or preparing evidence bundles for Supabase support escalation. Trigger with phrases like "supabase hard bug", "supabase mystery error", "supabase impossible to debug", "difficult supabase issue", "supabase deep debug". allowed-tools: Read, Grep, Bash(kubectl:), Bash(curl:), Bash(tcpdump:*) version: 1.0.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io
Supabase Advanced Troubleshooting
Prerequisites
- Access to production logs and metrics
- kubectl access to clusters
- Network capture tools available
- Understanding of distributed tracing
Instructions
Step 1: Collect Evidence Bundle
Run the comprehensive debug script to gather all relevant data.
Step 2: Systematic Isolation
Test each layer independently to identify the failure point.
Step 3: Create Minimal Reproduction
Strip down to the simplest failing case.
Step 4: Escalate with Evidence
Use the support template with all collected evidence.
Output
- Comprehensive debug bundle collected
- Failure layer identified
- Minimal reproduction created
- Support escalation submitted
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.