Ship a Next.js app to Vercel the production way: promote a tested preview to production, instant-rollback a bad release, build once with --prebuilt, run a staged/canary rollout with Rolling Releases (GA), and wire the deploy into CI.
Ship a Next.js app to Vercel the production way: promote a tested preview to production, instant-rollback a bad release, build once with --prebuilt, run a staged/canary rollout with Rolling Releases (GA), and wire the deploy into CI. Use when someone says "deploy to Vercel", "promote preview to production", "vercel promote", "roll back the deploy", "vercel rollback", "instant rollback", "canary release on Vercel", "rolling release", "--prebuilt build", "vercel deploy in GitHub Actions", or "set up CI for my Vercel project". Do NOT use to manage env vars or pull .env - use vercel-env-management instead; do NOT use to tune runtime/cold-start/ISR performance - use next-on-vercel-perf or vercel-edge-and-isr instead.This is the skill's description: the text your AI reads to decide when the skill applies.
vercel-deploy-pipeline/SKILL.md
---
name: Vercel Deploy Pipeline
description: Ship a Next.js app to Vercel the production way: promote a tested preview to production, instant-rollback a bad release, build once with --prebuilt, run a staged/canary rollout with Rolling Releases (GA), and wire the deploy into CI. Use when someone says "deploy to Vercel", "promote preview to production", "vercel promote", "roll back the deploy", "vercel rollback", "instant rollback", "canary release on Vercel", "rolling release", "--prebuilt build", "vercel deploy in GitHub Actions", or "set up CI for my Vercel project". Do NOT use to manage env vars or pull .env - use vercel-env-management instead; do NOT use to tune runtime/cold-start/ISR performance - use next-on-vercel-perf or vercel-edge-and-isr instead.
---
# Vercel Deploy Pipeline
You own the *ship* step of a curated "Next.js app on Vercel" workflow. This is not
the official Vercel CLI plugin re-stated - it sequences the platform into one
opinionated path: build a preview, prove it, promote the **same artifact** to
production, and keep a one-command escape hatch. The governing rule is **promote,
don't rebuild**: a deployment is immutable, so the bytes you tested in preview are
the exact bytes you put in front of users. Rebuilding to "release" reintroduces
every risk you just verified.
Trigger eagerly on anything about deploying a Next.js app to Vercel, promoting
preview to production, rolling back, building with `--prebuilt`, canary / staged
rollouts, or wiring `vercel` into CI. Hand off the adjacent concerns:
**vercel-env-management** owns env vars and `vercel env pull`;
**vercel-ai-gateway** owns model routing; **vercel-edge-and-isr** owns ISR / Cache
Components and runtime placement; **vercel-firewall-and-botid** owns WAF/BotID;
**next-on-vercel-perf** owns Fluid Compute cold-start and bundle tuning.
## Platform facts this skill assumes (current as of 2026)
… load the full skill through Skill MeClick to play with sound.