Ship Check
/ship-checkPre-deploy GO / WAIT / NO verdict for Next.js + Prisma on Railway. Catches the five mistakes that ship most disasters.
Install in one command
mkdir -p ~/.claude/skills/ship-check && curl -fsSL https://eliteaiadvantage.com/skills/ship-check/SKILL.md -o ~/.claude/skills/ship-check/SKILL.mdThen run /ship-check in Claude Code.
What it is
Ship Check is the pilot's pre-flight checklist for your stack. Most deploy disasters aren't exotic — they're the same five mistakes: typecheck didn't run, env var missing in prod, migration locks a big table, secret committed by accident, debug console.log left in. Ship Check catches all five before they reach Railway.
The skill does not deploy. It does not push. It tells you, with specific evidence, whether you're safe to ship — and gives you a single concrete next action either way.
Why it's useful
- →Front-loads the verdict — 🟢 GO / 🟡 WAIT / 🔴 NO — so you know in 10 seconds whether to ship.
- →Catches committed secrets, hardcoded API keys, and stranded debug code in changed files.
- →Audits new migrations for lock risks (NOT NULL on big tables, missing indexes, blocking operations).
- →Diffs process.env.X references against .env.example to flag undocumented vars.
- →Read-only by design — never modifies files, never pushes, never deploys.
When to use it
- •Before pushing to main on any production project.
- •Before clicking the Railway "deploy" button.
- •After a long branch where you've forgotten what changed.
- •When you're nervous about a deploy and want a structured second opinion.
How it helps with Claude
Without this skill, "is this safe to deploy?" gets a hand-wavy "looks good" or "should be fine." Ship Check forces the structured pass: specific files checked, specific risks flagged, single committed verdict. Claude stops giving false confidence and starts giving evidence-grounded GO/WAIT/NO calls with a line-numbered punch list.