Skip to content
SlashClone
DiscoverUse in ClaudeSubmit a link
Sign in
Made by@shipcheck

Deploy doctor

@shipcheck/deploy-doctor

Paste a failed Vercel or Netlify build log and get the most likely cause and a fix you can apply. Recognizes about twenty common failures: letter-case import errors, missing packages, missing env vars, prerender errors, window is not defined, lockfile drift, peer dependency conflicts, wrong Node version, out of memory, wrong output or root folder, oversized functions, and more.

SkillDevOpsv1.0.0 (latest)Tested
Use in Claude Save Like Clone Comment
Activity
New: be the first to try it
  1. 1# Deploy doctor
  2. 2
  3. 3Paste a failed Vercel or Netlify build log and get the most likely cause, why it worked on your machine, and the exact fix. It knows about twenty of the most common reasons builds fail, and Claude checks your project to confirm before changing anything.
  4. 4
  5. 5**For:** anyone whose app runs fine locally but fails to deploy. No DevOps background needed.
  6. 6
  7. 7## Example
  8. 8
  9. 9Input: a Vercel log that ends in `Error occurred prerendering page "/pricing"` after `Error: supabaseUrl is required.`
  10. 10
  11. 11Output (`out/deploy-triage.md`):
  12. 12
  13. 13```markdown
  14. 14Platform: Vercel | Framework: Next.js | Package manager: npm
  15. 15
  16. 16## Most likely cause: Environment variable missing at build time
  17. 17Line 18: Error: supabaseUrl is required.
  18. 18A required environment variable is not set for this build. Values in your
  19. 19local .env file are not uploaded to the host.
  20. 20
  21. 21Fix:
  22. 221. Add the variable in the host's project settings, under Environment
  23. 23 Variables, for the environment that failed (Production or Preview).
  24. 242. Variables with NEXT_PUBLIC_ or VITE_ prefixes are baked in at build
  25. 25 time, so redeploy after adding them.
  26. 26
  27. 27## Also seen: A page failed while being prerendered
  28. 28```
  29. 29
  30. 30Try it on the bundled logs: `node scripts/triage-log.mjs examples/vercel-nextjs-env.txt` or `examples/netlify-vite-case.txt`.
  31. 31
  32. 32## What it recognizes
  33. 33
  34. 34Letter-case imports, missing packages, Node modules on the edge, missing env vars, prerender errors, `window is not defined`, `useSearchParams` without Suspense, dynamic server usage, TypeScript and lint errors, lockfile drift, `ERESOLVE` peer conflicts, wrong Node version, out of memory, missing build script, command not found, wrong output or root folder, oversized functions, Prisma client not generated, and private package auth.
  35. 35
  36. 36## What it can access
  37. 37
  38. 38- Reads the log you save to `data/`, plus `package.json`, host config (`vercel.json`, `netlify.toml`), framework config, and your source folders to confirm the cause.
  39. 39- Writes the triage report to `out/`.
  40. 40- Can run your production build locally (`npm run build`, `pnpm run build`, or `yarn build`) to reproduce the error.
  41. 41- No network, no env vars. It never deploys or changes host settings.
  42. 42
  43. 43## Setup
  44. 44
  45. 45None. Needs Node 22 or later.
Sign in to comment on a line