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.zipInstalls 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,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
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_TOKENfor 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:
| Region | Location | Code |
|---|---|---|
| Washington, D.C. | US East | iad1 |
| San Francisco | US West | sfo1 |
| Paris | Europe | cdg1 |
| Tokyo | Asia | hnd1 |
| Sydney | Australia | syd1 |
| S. Paulo | South America | gru1 |
| London | Europe | lhr1 |
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
| Error | Cause | Solution |
|---|---|---|
DEPLOYMENT_BLOCKED | Deployment freeze or branch protection | Disable freeze in Settings or use --force |
| Promotion fails | Preview deployment has different env vars | Verify env vars match between preview and production |
| Rolling release stuck | Error threshold exceeded | Fix the code, then restart the rollout |
| Deploy hook returns 404 | Hook deleted or project ID wrong | Recreate the hook in Settings > Git |
| Region not available | Plan doesn't support multi-region | Upgrade to Pro or Enterprise |
Resources
- Deploying to Vercel
- Instant Rollback
- Rolling Releases
- Promoting Deployments
- Deploy Hooks
- Function Regions
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
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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| vercel-deploy-integration (this skill) | 1 | 27d | Review | Intermediate |
| vercel-deployment | 3 | 6mo | No flags | Intermediate |
| workflow | 4 | 2mo | Review | Intermediate |
| vercel-deploy | 4 | 5mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
vercel-deployment
davila7
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.
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.
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".
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".
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".
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".