VE

vercel-deploy-integration

Streamlines Vercel production deployment workflows including rollbacks, promotion of preview environments, and API-based deployments.

Install

mkdir -p .claude/skills/vercel-deploy-integration && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7724" && unzip -o skill.zip -d .claude/skills/vercel-deploy-integration && rm skill.zip

Installs to .claude/skills/vercel-deploy-integration

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Deploy and manage Vercel production deployments with promotion, rollback,
73 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Deploy applications to production via CLI or API
  • Promote preview deployments to production
  • Execute instant rollbacks to previous versions
  • Configure rolling releases for gradual traffic shifting
  • Set up multi-region function configurations

How it works

Deployments are managed through the Vercel CLI or API, allowing for traffic promotion, instant rollbacks by swapping pointers, and region-specific function execution.

Inputs & outputs

You give it
Deployment source code and configuration
You get back
Live production URL and deployment status

When to use vercel-deploy-integration

  • Deploy to production
  • Promote preview to production
  • Rollback failed releases
  • Configure multi-region functions

About this skill

Vercel Deploy Integration

Overview

Deploy Vercel applications to production using CLI, API, and Git-triggered workflows. Covers deployment promotion, instant rollback, rolling releases, multi-region function configuration, and deploy hooks for headless CMS integration.

Prerequisites

  • Vercel project linked and configured
  • Production environment variables set
  • Custom domain configured (optional)
  • VERCEL_TOKEN for API-based deployments

Instructions

Step 1: Production Deploy Methods

# Method 1: CLI direct production deploy
vercel --prod

# Method 2: Promote a preview deployment to production
vercel promote https://my-app-preview-xxx.vercel.app

# Method 3: API-based deployment
curl -X POST "https://api.vercel.com/v13/deployments" \
  -H "Authorization: Bearer $VERCEL_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "my-app",
    "target": "production",
    "gitSource": {
      "type": "github",
      "repoId": "123456789",
      "ref": "main",
      "sha": "'$(git rev-parse HEAD)'"
    }
  }'

# Method 4: Deploy Hook (for CMS-triggered rebuilds)
curl -X POST "https://api.vercel.com/v1/integrations/deploy/prj_xxx/hook_xxx"

Step 2: Instant Rollback

# Roll back to the previous production deployment (no rebuild)
vercel rollback

# Roll back to a specific deployment
vercel rollback dpl_xxxxxxxxxxxx

# Verify the rollback
vercel ls --prod
curl -s https://yourdomain.com/api/health | jq .

# Via API — promote a known-good deployment
curl -X POST "https://api.vercel.com/v9/projects/my-app/promote" \
  -H "Authorization: Bearer $VERCEL_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"deploymentId": "dpl_known_good_id"}'

Key points:

  • Instant rollback swaps production traffic without rebuilding
  • The rolled-back deployment retains its original environment variables
  • All production domains immediately point to the rolled-back deployment

Step 3: Rolling Releases (Gradual Rollout)

Configure rolling releases in the dashboard under Settings > Rolling Releases:

// vercel.json — rolling release config
{
  "rollingRelease": {
    "enabled": true,
    "stages": [
      { "targetPercentage": 10, "duration": 300 },
      { "targetPercentage": 50, "duration": 600 },
      { "targetPercentage": 100 }
    ]
  }
}

This routes 10% of traffic to the new deployment for 5 minutes, then 50% for 10 minutes, then 100%. If errors spike during any stage, rollback instantly.

Step 4: Multi-Region Function Configuration

// vercel.json — deploy functions to specific regions
{
  "regions": ["iad1", "sfo1", "cdg1", "hnd1"],
  "functions": {
    "api/user.ts": {
      "memory": 1024,
      "maxDuration": 30
    },
    "api/heavy-compute.ts": {
      "memory": 3008,
      "maxDuration": 60,
      "regions": ["iad1"]
    }
  }
}

Available regions:

RegionLocationCode
Washington, D.C.US Eastiad1
San FranciscoUS Westsfo1
ParisEuropecdg1
TokyoAsiahnd1
SydneyAustraliasyd1
S. PauloSouth Americagru1
LondonEuropelhr1

Step 5: Deploy Hooks (CMS Triggers)

Create deploy hooks in Settings > Git > Deploy Hooks:

# Create via dashboard, then trigger with POST
curl -X POST "https://api.vercel.com/v1/integrations/deploy/prj_xxx/hook_xxx"

# Common CMS integrations:
# Contentful — webhook URL → Vercel deploy hook
# Sanity — GROQ listener → deploy hook
# Strapi — lifecycle hook → deploy hook

Step 6: Deployment Monitoring

# List recent production deployments
vercel ls --prod --limit=5

# Check deployment state
curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \
  "https://api.vercel.com/v6/deployments?target=production&limit=5&projectId=prj_xxx" \
  | jq '.deployments[] | {uid, url, state, createdAt}'

# Monitor deployment logs in real-time
vercel logs https://yourdomain.com --follow

Deploy Lifecycle

git push main
  → Vercel builds (BUILDING)
    → Build succeeds (READY)
      → Traffic routes to new deployment
        → Old deployment kept for instant rollback

Output

  • Production deployment live via CLI, API, or Git push
  • Instant rollback configured to previous deployment
  • Rolling releases for gradual traffic shifting
  • Function regions optimized for user geography
  • Deploy hooks for CMS-triggered rebuilds

Error Handling

ErrorCauseSolution
DEPLOYMENT_BLOCKEDDeployment freeze or branch protectionDisable freeze in Settings or use --force
Promotion failsPreview deployment has different env varsVerify env vars match between preview and production
Rolling release stuckError threshold exceededFix the code, then restart the rollout
Deploy hook returns 404Hook deleted or project ID wrongRecreate the hook in Settings > Git
Region not availablePlan doesn't support multi-regionUpgrade to Pro or Enterprise

Resources

Next Steps

For webhook integration, see vercel-webhooks-events.

When not to use it

  • When deploying to non-Vercel platforms
  • When the project is not linked to a Vercel account

Prerequisites

Vercel project linked and configuredProduction environment variables setVERCEL_TOKEN for API-based deployments

Limitations

  • Multi-region configuration requires specific plan support
  • Rollback depends on the availability of previous deployment artifacts

How it compares

This method enables instant traffic switching and rolling releases without requiring a full rebuild of the application.

Compared to similar skills

vercel-deploy-integration side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
vercel-deploy-integration (this skill)127dReviewIntermediate
vercel-deployment36moNo flagsIntermediate
workflow42moReviewIntermediate
vercel-deploy45moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

You might also like

vercel-deployment

davila7

Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.

359

workflow

vercel

Creates durable, resumable workflows using Vercel's Workflow DevKit. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow devkit", or step-based orchestration.

431

vercel-deploy

openai

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

422

vercel-multi-env-setup

jeremylongshore

Configure Vercel across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Vercel configurations. Trigger with phrases like "vercel environments", "vercel staging", "vercel dev prod", "vercel environment setup", "vercel config by env".

13

ideogram-deploy-integration

jeremylongshore

Deploy Ideogram integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying Ideogram-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy ideogram", "ideogram Vercel", "ideogram production deploy", "ideogram Cloud Run", "ideogram Fly.io".

12

langfuse-deploy-integration

jeremylongshore

Deploy Langfuse with your application across different platforms. Use when deploying Langfuse to Vercel, AWS, GCP, or Docker, or integrating Langfuse into your deployment pipeline. Trigger with phrases like "deploy langfuse", "langfuse Vercel", "langfuse AWS", "langfuse Docker", "langfuse production deploy".

12

Search skills

Search the agent skills registry