deployments-cicd

Guides Vercel deployments, promotions, rollbacks, and CI/CD pipeline configuration.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/dsgalkar/dnyaneshwar_portfolio --skill deployments-cicd-dsgalkar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployments-cicd
Source: https://github.com/dsgalkar/dnyaneshwar_portfolio/tree/main/.agents/plugins/vercel/skills/deployments-cicd
Command: npx skills add https://github.com/dsgalkar/dnyaneshwar_portfolio --skill deployments-cicd-dsgalkar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying to Vercel through custom CI/CD pipelines involves many moving parts: choosing between preview and production targets, deciding when to use prebuilt builds, promoting validated deployments, and wiring up GitHub Actions, GitLab CI, or Bitbucket Pipelines correctly. This Skill provides expert guidance so you avoid misconfigured workflows, hanging pipelines, and failed builds. ## Core Features & Use Cases - Deployment Command Guidance: Covers preview deploys, production deploys, prebuilt builds, promotion, rollback, and log inspection with the Vercel CLI. - CI/CD Pipeline Templates: Provides ready-to-adapt workflow configurations for GitHub Actions, GitLab CI, and Bitbucket Pipelines, including PR preview comments and promote-after-test patterns. - Troubleshooting & Best Practices: Documents common build errors, required environment variables, OIDC federation usage, and post-deploy observability checks. - Use Case: You want every pull request to produce a preview URL and every merge to main to run tests before promoting to production. This Skill walks you through building that exact pipeline. ## Quick Start Ask the assistant to set up a GitHub Actions workflow that builds and deploys your project to Vercel production on every push to main.

Frequently Asked Questions about deployments-cicd

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

FAQPage Schema
How do I deploy to Vercel from GitHub Actions?

Install the Vercel CLI in your workflow, then run vercel pull, vercel build --prod, and vercel deploy --prebuilt --prod, each with --token using a VERCEL_TOKEN secret. You also need VERCEL_ORG_ID and VERCEL_PROJECT_ID configured as CI secrets.

What is the difference between vercel promote and vercel deploy --prod?

vercel promote instantly re-points the production alias to an existing preview deployment without rebuilding. vercel deploy --prod creates a brand new production deployment. Use promote when a preview has already been validated.

When should I use vercel deploy --prebuilt?

Use --prebuilt in custom CI pipelines where you control the build step with vercel build, want CI-level build caching, or need to run tests between build and deploy. It deploys only the build output without a remote build.

Does Vercel OIDC federation replace VERCEL_TOKEN in CI pipelines?

No. OIDC federation lets deployed Vercel functions authenticate to external services like AWS or GCP without static secrets. All CLI commands in CI such as vercel pull, build, and deploy still require --token with VERCEL_TOKEN.

Why does my Vercel build fail with ERR_PNPM_OUTDATED_LOCKFILE?

This error means your lockfile does not match package.json. Run pnpm install locally to regenerate the lockfile, commit it, and redeploy. Other common failures include misconfigured rootDirectory and invalid next.config.js syntax.

How do I roll back a Vercel production deployment?

Run vercel rollback to return to the previous production deployment, or vercel rollback <deployment-url-or-id> to target a specific deployment. This re-points the production alias without rebuilding.