Verified:GitHub

deployments-cicd

Guide Vercel deployments and CI/CD across GitHub Actions, GitLab CI, and Bitbucket Pipelines.

Updated May 16, 2026

Search Tags:#ci/cd #rollback #github actions #vercel #promotion #deployments #prebuilt deploy

One-click install

npx skills add https://github.com/MohammedHTahir/vibe-coding-platform --skill deployments-cicd-mohammedhtahir

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: deployments-cicd
Source: https://github.com/MohammedHTahir/vibe-coding-platform/tree/main/.kiro/vercel-plugin/skills/deployments-cicd
Command: npx skills add https://github.com/MohammedHTahir/vibe-coding-platform --skill deployments-cicd-mohammedhtahir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you deploy, promote, rollback, and inspect Vercel releases reliably while avoiding common CI/CD misconfigurations that cause broken builds, broken previews, or slow rollbacks.

Core Features & Use Cases

Vercel deployment workflow: Covers preview vs production flows using vercel deploy and vercel --prod, including force redeploys.
Promotion and rollback control: Explains when to use vercel promote for instant production switches and how to rollback with vercel rollback (including targeting a specific deployment).
CI/CD integration patterns: Provides GitHub Actions, GitLab CI, and Bitbucket Pipelines examples, including required CI environment variables and secure auth practices.
Operational visibility: Shows how to inspect deployments and review logs using vercel inspect, vercel ls, and vercel logs with follow for real-time debugging.

Quick Start

Use the deployments-cicd Skill to generate a CI workflow that deploys build output using vercel build and vercel deploy --prebuilt to production, with the required Vercel CLI token environment variables.

Frequently Asked Questions about deployments-cicd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up GitHub Actions to deploy prebuilt Vercel artifacts?▼

Use vercel build followed by vercel deploy --prebuilt in your GitHub Actions workflow to upload cached build artifacts. Configure Vercel CLI token environment variables for authentication before executing the deployment commands.

What is the difference between vercel promote and vercel deploy for production releases?▼

Vercel promote switches production traffic to an existing deployment instantly without rebuilding, while vercel deploy creates a new build. Use promote for rapid production switches and vercel rollback to revert to a specific previous deployment target.

Does this Vercel CI/CD workflow support GitLab CI and Bitbucket Pipelines?▼

Yes, the Vercel deployment workflow supports GitLab CI and Bitbucket Pipelines alongside GitHub Actions. You must align Vercel CLI commands with correct token-based authentication and configure required CI environment variables for each specific platform.

How do I inspect Vercel deployment logs for debugging?▼

Debug Vercel deployments using vercel inspect, vercel ls, and vercel logs commands. Apply vercel logs with follow for real-time debugging of preview and production releases during CI/CD pipeline execution.

Why are my Vercel preview deployments broken in CI?▼

Broken Vercel preview deployments in CI are typically caused by misconfigured environment variables or incorrect token-based authentication. Ensure your pipeline reads environment variables from .vercel/project.json and uses the correct Vercel CLI token.