vercel-advanced-troubleshooting
Apply Vercel advanced debugging techniques for hard-to-diagnose issues.Use when standard troubleshooting fails, investigating complex race conditions,or preparing evidence bundles for Vercel support escalation.Trigger with phrases like "vercel hard bug", "vercel mystery error","vercel impossible to debug", "difficult vercel issue", "vercel deep debug".
When & Why to Use This Skill
This Claude skill provides advanced Vercel troubleshooting capabilities designed for senior developers and SREs to resolve complex, hard-to-diagnose cloud infrastructure issues. It automates the collection of deep-dive diagnostic data, including network captures and cluster logs, to identify race conditions and streamline the creation of evidence bundles for Vercel support escalation.
Use Cases
- Investigating Complex Race Conditions: Systematically isolate and identify intermittent timing issues within Vercel deployments using advanced debugging scripts.
- Vercel Support Escalation: Automatically generate comprehensive evidence bundles, including logs and network traces, to provide support teams with high-quality diagnostic data.
- Deep Network Diagnostics: Execute low-level network analysis using tools like tcpdump and kubectl to troubleshoot 'impossible to debug' connectivity or latency errors.
- Root Cause Analysis (RCA): Perform systematic isolation of failure layers to create minimal reproduction cases for production-level incidents.
| name | vercel-advanced-troubleshooting |
|---|---|
| description | | |
| allowed-tools | Read, Grep, Bash(kubectl:*), Bash(curl:*), Bash(tcpdump:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Vercel 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.