vercel-deployments-builds
Vercel deployment lifecycle for builds, deployments, previews, release phases, and rollback. Use when configuring build output, deployment workflows, or release controls on Vercel.
What this skill does
# Vercel Deployments and Builds Skill
---
progressive_disclosure:
entry_point:
summary: "Deployments and builds on Vercel: build pipeline, deployment environments, deploy hooks, release phases, checks, and rollback."
when_to_use:
- "When configuring build and deployment workflows"
- "When using preview and production deployments"
- "When controlling releases and rollbacks"
quick_start:
- "Connect a Git repository"
- "Review build and deployment settings"
- "Use previews for every branch"
- "Promote to production and monitor"
token_estimate:
entry: 90-110
full: 3800-4800
---
## Overview
Vercel deployments and builds cover the full lifecycle from source changes to production releases with automated previews and rollback controls.
## Deployments
- Use preview deployments for every branch or pull request.
- Promote deployments to production when ready.
- Configure deployment retention where needed.
## Builds
- Define build settings per project.
- Use the Build Output API for custom build output.
- Review build logs for failures.
## Release Controls
- Use release phases for controlled rollouts.
- Use instant rollback when a deployment causes regressions.
- Add deployment checks for quality gates.
## Automation
- Trigger deployments with deploy hooks.
- Add a deploy button for fast deploys.
## Complementary Skills
When using this skill, consider these related skills (if deployed):
- **vercel-functions-runtime**: Functions and runtime behavior for deployments.
- **vercel-networking-domains**: Domains, routing, and CDN behavior.
- **vercel-observability**: Logs and tracing for deployment issues.
*Note: Complementary skills are optional. This skill is fully functional without them.*
## Resources
**Vercel Docs**:
- Deployments: https://vercel.com/docs/deployments
- Builds: https://vercel.com/docs/builds
- Build Output API: https://vercel.com/docs/build-output-api
- Deploy hooks: https://vercel.com/docs/deploy-hooks
- Deploy button: https://vercel.com/docs/deploy-button
- Release phases: https://vercel.com/docs/release-phases
- Deployment checks: https://vercel.com/docs/deployment-checks
- Instant rollback: https://vercel.com/docs/instant-rollback
- Deployment retention: https://vercel.com/docs/deployment-retention
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.