Deploy doctor

Name: Deploy doctor
Author: @shipcheck

@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
Installs: 0 installs
Likes: 0 likes
Clones: 0 clones

Clones

No clones yet.

Make your own version with slashclone clone @shipcheck/deploy-doctor. The original author keeps the credit.

0 clones · Made by @shipcheck

Use in Claude

Claude Code

/kit add @shipcheck/deploy-doctor

CLI

slashclone add @shipcheck/deploy-doctor

Codex

slashclone add @shipcheck/deploy-doctor --agent codex

Not enforced. Codex does not enforce the permissions this kit declares.

Cursor

slashclone add @shipcheck/deploy-doctor --agent cursor

Not enforced. Cursor does not enforce the permissions this kit declares.

claude.ai and the desktop app

Download for Claude

Not enforced. claude.ai and the Claude desktop app do not enforce the permissions this kit declares. How to upload it

As a file

Download .kit

One file with everything in it. slashclone add ./file.kit checks it against this page before installing.

Review before installing

Set up SlashClone in Claude

Health

No keep-alive checks yet

Checks run weekly once someone keeps the kit installed.

Run reports are off

Safety

Scan passed
Not reviewed yet
Tests pass (3 of 3)

This kit reads ./data/**, ./package.json, ./vercel.json, ./netlify.toml, ./next.config.*, ./vite.config.*, ./.nvmrc, ./src/**, ./app/**, ./pages/**, ./components/**, ./lib/**, writes to ./data/**, ./out/** and runs node scripts/triage-log.mjs, npm run build, pnpm run build, yarn build. Install it?

Full scan and review

Similar kits

Dev prod parity rule
@slashclone
A CLAUDE.md rule that keeps development and production behaving the same: prefer explicit environment flags over NODE_ENV checks, and write down every unavoidable difference in the deploy guide in the same change.
Env secrets check
@shipcheck
Check your repo for leaked secrets before you push or launch: .env files git tracks or will pick up, .env files hiding in git history, server keys behind NEXT_PUBLIC_ or VITE_ prefixes that ship to the browser, provider key shapes (Stripe, AWS, GitHub, OpenAI, Anthropic, Supabase service_role), and passwords hardcoded in code. Reports names and redacted hints, never the values.
Launch checklist
@shipcheck
A pre-launch check for your first real app. Reads your project, detects the stack (Supabase, Stripe, Next.js, auth, email), and writes a checklist split into blockers, first-week items, and later, with evidence from your code for each item it could verify. Covers data access, payments, secrets, auth, abuse limits, errors and monitoring, backups, email deliverability, legal pages, and SEO basics.
Pin dependencies safely
@slashclone
Before adding or upgrading a package: confirm the version exists, is the latest stable release, and is at least 14 days old, then pin it exactly and commit the lockfile. A simple guard against typosquats and freshly compromised releases.

Link

https://slashclone.dev/@shipcheck/deploy-doctor

README badge

[![Install with SlashClone](https://slashclone.dev/badge/shipcheck/deploy-doctor.svg)](https://slashclone.dev/@shipcheck/deploy-doctor)

Embed

<iframe src="https://slashclone.dev/embed/shipcheck/deploy-doctor" width="480" height="200" title="@shipcheck/deploy-doctor" loading="lazy"></iframe>

Share card image

More from @shipcheck

Supabase rls audit
Audit row level security in your Supabase migrations before you launch. Finds tables with RLS off, policies that let anyone write, policies that trust user_metadata, views that skip RLS, and risky SECURITY DEFINER functions, then drafts a fix migration for you to review. Reads .sql files only and never touches your database.
Stripe webhook hardening
Find your Stripe webhook handlers and harden them: verify the Stripe-Signature header, use the raw body, keep the signing secret in env, process each event once, reject bad signatures with 400, and fulfill orders from the webhook rather than the success page. Reads your code and proposes diffs; never calls Stripe.
Launch checklist
A pre-launch check for your first real app. Reads your project, detects the stack (Supabase, Stripe, Next.js, auth, email), and writes a checklist split into blockers, first-week items, and later, with evidence from your code for each item it could verify. Covers data access, payments, secrets, auth, abuse limits, errors and monitoring, backups, email deliverability, legal pages, and SEO basics.
Env secrets check
Check your repo for leaked secrets before you push or launch: .env files git tracks or will pick up, .env files hiding in git history, server keys behind NEXT_PUBLIC_ or VITE_ prefixes that ship to the browser, provider key shapes (Stripe, AWS, GitHub, OpenAI, Anthropic, Supabase service_role), and passwords hardcoded in code. Reports names and redacted hints, never the values.

See all of @shipcheck's kits

Report this kit