Investigate Vercel deployment errors using Vercel CLI. Use when user shares a Vercel deployment error, build failure, or deployment URL that needs debugging.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
vercel whoamiIf error "No credentials found", prompt user to run vercel login in their terminal (interactive).
vercel list <project-name> --scope <team-name>Find the failing deployment URL (status: Error or Building).
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| 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 |
vercel inspect <deployment-url> --scope <team-name>f734087
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.