debug prod issues

Diagnose Vercel production issues via live logs, deployments, and Neon Postgres.

249|47|Updated Nov 5, 2024
One-click install
npx skills add https://github.com/different-ai/agent-bank --skill debug-prod-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug prod issues
Source: https://github.com/different-ai/agent-bank/tree/main/.opencode/skill/debug-prod-issues
Command: npx skills add https://github.com/different-ai/agent-bank --skill debug-prod-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps diagnose and fix production issues on Vercel by providing guided steps to access live logs, verify deployments, and inspect production databases.

Core Features & Use Cases

  • Live log streaming: Monitor real-time function logs to identify failures.
  • Deployment health checks: Inspect latest deployments to confirm status and wait for readiness.
  • Database debugging: Connect to Neon Postgres; inspect tables and data to verify production state.
  • Environment validation: Verify environment variables and configuration across environments to reproduce issues.

Quick Start

Run the following steps to begin debugging production issues in your Vercel project:

  • Stream live logs: vercel logs www.your-app --scope your-team
  • List deployments and wait for readiness: LATEST=$(vercel ls --scope your-team 2>/dev/null | head -1); vercel inspect "$LATEST" --scope your-team --wait --timeout 5m
  • Connect to the Neon production database after loading production env: load .env.production.local and run a small diagnostic script against the database.

Frequently Asked Questions about debug prod issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug production issues on Vercel using live logs?

Debug production issues on Vercel by streaming live function logs via the Vercel CLI using the vercel logs command with your app and team scope to identify real-time failures.

How do I check if my Vercel deployment is ready and healthy?

Check Vercel deployment health by listing recent deployments with vercel ls, then running vercel inspect with the wait flag and a timeout to confirm the latest deployment reaches a ready status.

Can I connect to a Neon Postgres production database for debugging?

Yes, you can debug a Neon Postgres production database by loading your .env.production.local variables and running a one-off diagnostic script to inspect tables and verify production data state.

What's the best way to reproduce Vercel API errors locally?

Reproduce Vercel API errors by validating environment configurations across environments, loading production dotenv files locally, and executing diagnostic scripts against your live resources to match the production context.

Do I need the Vercel CLI to inspect deployment logs and database state?

Yes, diagnosing production issues requires the Vercel CLI to access live logs and inspect deployment readiness, alongside Neon DB access and dotenv configurations to connect and run database diagnostic scripts.