vercel-debug-bundle

•

2k2653 months ago

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".

Quick Install

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

Instructions

Vercel Debug Bundle

Overview

Collect a comprehensive debug bundle containing deployment state, function logs, environment configuration, and build output for Vercel support escalation or team troubleshooting.

Current State

!vercel --version 2>/dev/null || echo 'Vercel CLI not installed' !node --version 2>/dev/null || echo 'Node.js N/A'

Prerequisites

Vercel CLI installed and authenticated
Access to the affected deployment
jq for JSON processing (recommended)

Instructions

Step 1: Collect Deployment Information

#!/usr/bin/env bash
set -euo pipefail

DEPLOY_URL="${1:-$(vercel ls --json 2>/dev/null | jq -r '.[0].url')}"
BUNDLE_DIR="vercel-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE_DIR"

echo "=== Collecting debug bundle for: $DEPLOY_URL ==="

# Deployment inspection
vercel inspect "$DEPLOY_URL" > "$BUNDLE_DIR/inspect.txt" 2>&1 || true

# Deployment details via API
curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \
  "https://api.vercel.com/v13/deployments/$DEPLOY_URL" \
  | jq '{uid, name, state, target, readyState, errorMessage, meta, regions}' \
  > "$BUNDLE_DIR/deployment.json" 2>/dev/null || true

Loading…

Related Skills

skill-creator

Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.

367,360

skill-creator

Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.

367,309

1password

Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.

365,915

himalaya

CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).

365,885

Tags & Topics

aiautomationclaude-codedevopsmcpai-agents

Vercel Debug Bundle

Overview

Collect a comprehensive debug bundle containing deployment state, function logs, environment configuration, and build output for Vercel support escalation or team troubleshooting.

Current State

!vercel --version 2>/dev/null || echo 'Vercel CLI not installed' !node --version 2>/dev/null || echo 'Node.js N/A'

Prerequisites

Vercel CLI installed and authenticated
Access to the affected deployment
jq for JSON processing (recommended)

Instructions

Step 1: Collect Deployment Information

#!/usr/bin/env bash
set -euo pipefail

DEPLOY_URL="${1:-$(vercel ls --json 2>/dev/null | jq -r '.[0].url')}"
BUNDLE_DIR="vercel-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE_DIR"

echo "=== Collecting debug bundle for: $DEPLOY_URL ==="

# Deployment inspection
vercel inspect "$DEPLOY_URL" > "$BUNDLE_DIR/inspect.txt" 2>&1 || true

# Deployment details via API
curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \
  "https://api.vercel.com/v13/deployments/$DEPLOY_URL" \
  | jq '{uid, name, state, target, readyState, errorMessage, meta, regions}' \
  > "$BUNDLE_DIR/deployment.json" 2>/dev/null || true

File	Contents
`inspect.txt`	Deployment inspection output
`deployment.json`	Deployment state, target, errors
`function-logs.txt`	Recent function invocation logs
`events.json`	Deployment event timeline
`build-info.json`	Build configuration and output
`routes-functions.json`	Route and function mapping
`env-vars-list.txt`	Environment variable names (no values)
`vercel.json`	Project configuration
`package-summary.json`	Dependencies and versions
`environment.txt`	System info (Node, CLI, OS)
`platform-status.json`	Vercel platform status at time of capture

Error	Cause	Solution
`vercel inspect` fails	Deployment deleted or token expired	Use API directly with curl
`jq: command not found`	jq not installed	`apt install jq` or `brew install jq`
Empty function logs	Function not invoked or log retention expired	Check Observability tab in dashboard
VERCEL_TOKEN not set	Not authenticated for API calls	Export token or run `vercel login`

vercel-debug-bundle

Vercel Debug Bundle

Overview

Current State

Prerequisites

Instructions

Step 1: Collect Deployment Information

Related Skills

skill-creator

skill-creator

1password

himalaya

Vercel Debug Bundle

Overview

Current State

Prerequisites

Instructions

Step 1: Collect Deployment Information

Step 2: Collect Function Logs

Step 3: Collect Build Output

Step 4: Collect Environment State (Redacted)

Step 5: Check Vercel Status Page

Step 6: Package the Bundle

Bundle Contents Reference

Support Ticket Template

Output

Error Handling

Resources

Next Steps

Related Skills

skill-creator

skill-creator

1password

himalaya

Related Skills

skill-creator

skill-creator

1password

himalaya