Menu

Individual skill

vercel-deploy-pipeline

0upvotes

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.

skills/vercel-deploy-pipeline/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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`;
Back to top