vercel-debug

Investigate Vercel deployment errors using Vercel CLI. Use when user shares a Vercel deployment error, build failure, or deployment URL that needs debugging.

Quality

88%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Vercel Deployment Debugging

Workflow

1. Check authentication

vercel whoami

If error "No credentials found", prompt user to run vercel login in their terminal (interactive).

2. List recent deployments

vercel list <project-name> --scope <team-name>

Find the failing deployment URL (status: Error or Building).

3. Get build logs

vercel inspect <deployment-url> --logs --scope <team-name>

Add --wait to wait for in-progress builds:

vercel inspect <deployment-url> --logs --scope <team-name> --wait

4. Common errors

Error	Cause	Fix
Mixed Routing Properties	`routes` and `rewrites` mixed in vercel.json	Use only `rewrites` (new format)
Cannot find module	Package not built before dependent	Add to build command or use turbo
Build Command > 256 chars	Command too long	Use `pnpm build` with turbo/nx

5. Get deployment info (without logs)

vercel inspect <deployment-url> --scope <team-name>

Repository: yahsan2/static-admin
Commit: f734087

Last updated: about 2 months ago
Created: about 2 months ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.