askill
ship

shipSafety 90Repository

Pre-deploy checklist with review, security, and test verification. Use when ready to deploy.

2 stars
1.2k downloads
Updated 2/9/2026

Package Files

Loading files...
SKILL.md

Ship Workflow

Complete deployment pipeline: pre-flight → security → deploy → verify → report.

Step 1: Pre-flight Checks

Run ALL checks in parallel:

npm run typecheck          # Must pass
npm run build              # Must pass
npm run test               # Run if available
git status --short         # Warn if uncommitted changes
ResultAction
Build failsStop — fix errors first
Typecheck failsStop — fix types first
Tests failStop — fix tests first
Uncommitted changesWarn user, ask if they want to commit (use git directly, do NOT invoke the commit skill)
All passContinue to Step 2

Step 2: Security Scan

Run before every deploy (uses security skill):

  • No hardcoded API keys, tokens, or secrets in code
  • .env files not committed (check .gitignore)
  • Supabase RLS enabled on all public tables
  • Input validation on all user-facing forms
  • No dangerouslySetInnerHTML without sanitization
  • Auth checks on protected routes

If critical issues found, fix before deploying.

Step 3: Auto-detect Deploy Target

Check in order:

  1. vercel.json or .vercel/ exists → Vercel
  2. netlify.toml exists → Netlify
  3. supabase/functions/ exists → Supabase Edge Functions (deploy alongside)
  4. User specified "ship to X" → Use X
  5. None found → Default to Vercel

Do not ask which platform — detect or default.

Step 4: Deploy

Vercel

# Preview first (recommended)
npx vercel --yes

# If preview looks good, promote to production
npx vercel --prod --yes

Netlify

npx netlify deploy --prod

Supabase Edge Functions

# Single function
supabase functions deploy [function-name] --project-ref [ref]

# All functions
supabase functions deploy --project-ref [ref]

Environment Variables

Before deploying, verify env vars are set on the platform:

# Vercel
vercel env ls

# Netlify
netlify env:list

# Supabase
supabase secrets list --project-ref [ref]

Missing env vars = broken deploy. Check before shipping.

Step 5: Post-Deploy Verification (MANDATORY - never skip)

A successful deploy does NOT mean the app works. Verify after deploying.

Automated Checks (agent-browser)

agent-browser open [DEPLOY_URL]
agent-browser snapshot -i

Verification Checklist

CheckHowPass Criteria
Page loadsOpen deploy URLNo 404, no blank screen
No console errorsagent-browser snapshotZero errors in console
Auth flowLogin → protected page → logoutAll transitions work
Critical pathComplete main user actionEnd-to-end success
API callsCheck network tabNo 500s, no CORS errors
Mobile layoutResize to 375px widthSidebar hidden, grids stacked, no overflow

What to Test by App Type

App TypeCritical Paths
SaaSSign up → onboard → core action → billing
E-commerceBrowse → add to cart → checkout
ContentLoad → search → read → interact
APIHealth endpoint → auth → CRUD operations

If Verification Fails

  1. Console errors → Check browser console, fix and redeploy
  2. API failures → Check env vars on platform, check CORS settings
  3. Auth broken → Check OAuth redirect URLs match deploy URL
  4. Blank page → Check build output, check base path config

Step 6: Rollback (if needed)

# Vercel - instant rollback to previous
vercel rollback

# Netlify
netlify rollback

# Supabase Edge Functions - redeploy previous version
git log --oneline supabase/functions/
git checkout [prev-commit] -- supabase/functions/
supabase functions deploy --project-ref [ref]

Step 7: Report

Update prd.json and report to user:

Shipped to: [URL]
Platform: Vercel/Netlify
Build: passed
Security: passed
Verification: [pass/fail]
  - Page loads: ✓
  - Console errors: none
  - Auth flow: ✓
  - Critical path: ✓

If any verification failed, list specific failures and next steps.


Integration

SkillRole in Ship
reviewCode quality check (auto-loaded via requires)
securityVulnerability scan (auto-loaded via requires)
testRun tests before deploy (auto-loaded via requires)
deployDeploy patterns and CI/CD pipeline reference

Install

Download ZIP
Requires askill CLI v1.0+

AI Quality Score

89/100Analyzed 2/24/2026

High-quality deployment skill with comprehensive 7-step workflow. Strong clarity (95) and actionability (90) with detailed commands for Vercel/Netlify/Supabase, decision tables, and mandatory post-deploy verification. Good safety (90) includes security scanning and rollback procedures. Completeness (85) covers full pipeline but limited to npm ecosystem. Moderate reusability (75) due to node-specific assumptions. Bonus points from R3 (triggers), R5 (structured steps), R6 (tags), R10 (skills folder), R11 (high-density reference). Well-suited for general deployment automation."

90
95
75
85
90

Metadata

Licenseunknown
Version-
Updated2/9/2026
Publisherdjnsty23

Tags

apici-cdgithub-actionssecuritytesting