Fix a failed Vercel or Netlify deploy
Fix a deploy that works locally but fails on Vercel or Netlify: paste the build log, get the likely cause and the fix. Finds the first real error and matches about twenty common failures, like letter-case imports, missing packages or env vars, window is not defined, lockfile drift, wrong Node version, and out of memory. Checks your code and asks before changing anything.
- Activity
- New: be the first to try it
Will this work for me?
- Effort
- Needs about 10 minutes of setupOur guess from what the kit says it needs.
- Works in
- Claude Code, claude.ai and the desktop app
- You need
Vercel account: setup steps
- What it is
- This kit works with your own Vercel account.
- Where to get it
- Sign in to Vercel, or make a free account if it offers one. Go to Vercel
Netlify account: setup steps
How this works
- It is a skill: written instructions Claude reads when your request matches what the skill is for. You do not call it by name; just ask for the task.
- While it works, it reads and changes files in the places it lists, nowhere else.
- It runs these commands on your computer: node scripts/triage-log.mjs, npm run build, pnpm run build, yarn build.
- Nothing runs until you choose to use it, and you can remove it any time.
What it can access
What this kit says it will touch, the same list you see before you add it. These are its Permissions: What a kit is allowed to touch on your computer or accounts, such as reading a folder or using the internet. You see them before you add it.. In Claude Code they become rules, so Claude stops anything not on the list.
Command
Runs the command: node scripts/triage-log.mjs (with any arguments, without asking)
Command
Runs the command: npm run build (with any arguments, without asking)