Deployments Cicd

Covers Vercel's deployment workflow from preview to production, including the full command set (deploy, promote, rollback, inspect) and CI/CD integration patterns for GitHub Actions, GitLab, and Bitbucket. The standout bit is the prebuilt workflow guidance, which separates build from deploy so you can gate production on tests. Also clears up a common confusion: OIDC federation is for runtime service auth in your functions, not for authenticating the CLI in CI pipelines. You still need VERCEL_TOKEN for that. Useful if you're setting up a custom pipeline or need to understand when to promote versus redeploy.

skills.sh installs: 333
GitHub stars: 183
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add vercel-labs/vercel-plugin --skill deployments-cicd --agent claude-code

Installs into .claude/skills of the current project.

Files

Vercel Deployments & CI/CD

You are an expert in Vercel deployment workflows — vercel deploy, vercel promote, vercel rollback, vercel inspect, vercel build, and CI/CD pipeline integration with GitHub Actions, GitLab CI, and Bitbucket Pipelines.

Deployment Commands

Preview Deployment

# Deploy from project root (creates preview URL)
vercel

# Equivalent explicit form
vercel deploy

Git pushes to non-production branches make previews. A project's first deploy goes to production. To undo it, ask the user, then run vercel remove <id> --yes.

Production Deployment

# Deploy directly to production
vercel --prod
vercel deploy --prod

# Force a new deployment (skip cache)
vercel --prod --force

Build Locally, Deploy Build Output

# Build locally (uses preview env vars by default)
vercel build

# Build with production env vars
vercel build --prod

# Deploy only the build output (no remote build)
vercel deploy --prebuilt
vercel deploy --prebuilt --prod

When to use --prebuilt: Custom CI pipelines where you control the build step, need build caching at the CI level, or need to run tests between build and deploy.

SKILL.md on GitHub