home / skills / jeremylongshore / claude-code-plugins-plus-skills / vercel-debug-bundle

vercel-debug-bundle skill

safe

/plugins/saas-packs/vercel-pack/skills/vercel-debug-bundle

This skill collects Vercel debug evidence for support tickets and troubleshooting, packaging environment, logs, and config into a searchable tarball.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill vercel-debug-bundle

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

1.2 KB

---
name: vercel-debug-bundle
description: |
  Execute collect Vercel debug evidence for support tickets and troubleshooting.
  Use when encountering persistent issues, preparing support tickets,
  or collecting diagnostic information for Vercel problems.
  Trigger with phrases like "vercel debug", "vercel support bundle",
  "collect vercel logs", "vercel diagnostic".
allowed-tools: Read, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---

# Vercel Debug Bundle

## Prerequisites
- Vercel SDK installed
- Access to application logs
- Permission to collect environment info


See `{baseDir}/references/implementation.md` for detailed implementation guide.

## Output
- `vercel-debug-YYYYMMDD-HHMMSS.tar.gz` archive containing:
  - `summary.txt` - Environment and SDK info
  - `logs.txt` - Recent redacted logs
  - `config-redacted.txt` - Configuration (secrets removed)

## Error Handling

See `{baseDir}/references/errors.md` for comprehensive error handling.

## Examples

See `{baseDir}/references/examples.md` for detailed examples.

## Resources
- [Vercel Support](https://vercel.com/docs/support)
- [Vercel Status](https://www.vercel-status.com)

Overview

This skill collects a compact Vercel debug bundle to accelerate troubleshooting and support tickets. I gather environment details, redacted logs, and sanitized configuration into a timestamped archive ready to attach to support requests. The output is a single .tar.gz file that preserves privacy by removing secrets.

How this skill works

I use the Vercel SDK and available access to your application logs to extract runtime environment info, SDK versions, recent logs, and configuration settings. Sensitive values are automatically redacted before packaging. The result is a vercel-debug-YYYYMMDD-HHMMSS.tar.gz archive containing summary.txt, logs.txt, and config-redacted.txt for easy inspection and upload to Vercel support.

When to use it

When encountering persistent or intermittent deployment/runtime errors that are hard to reproduce locally
Before opening a Vercel support ticket to provide concise, contextual diagnostics
When you need a sanitized snapshot of logs and config to share with teammates or third-party maintainers
During post-incident reviews to preserve state and evidence for root-cause analysis
When automated monitoring alerts require additional context beyond metrics

Best practices

Ensure the Vercel SDK is installed and the executing identity has permission to read application logs and config
Run the collection close to the time of the failure to capture relevant logs and transient state
Review the redacted outputs briefly before sharing to confirm no secrets remain
Limit collection scope to the affected project or deployment to reduce noise
Keep the archive retention short and delete it once the ticket is resolved

Example use cases

Collecting evidence for a support ticket after repeated 500 responses on production
Sharing a sanitized bundle with a colleague to reproduce a client-reported bug
Packaging logs and environment details for a third-party integration failing in a specific region
Capturing deployment config and recent logs immediately after a CI/CD rollback
Generating a reproducible diagnostic snapshot for long-running performance investigations

FAQ

What does the bundle contain?

The archive includes summary.txt (environment and SDK info), logs.txt (recent redacted logs), and config-redacted.txt (configuration with secrets removed).

Are secrets removed automatically?

Yes. The tool redacts common secret patterns from logs and configuration before packaging, but you should still review outputs before sharing.

What permissions are required?

Read access to application logs and permission to query environment/config via the Vercel SDK are required.