What problem does it solve? Deploying to Vercel through custom CI/CD pipelines involves many moving parts: choosing between preview and production deploys, deciding when to use --prebuilt, wiring up GitHub Actions or GitLab CI correctly, and handling promotions or rollbacks safely. This Skill provides expert guidance so you avoid misconfigured workflows, hanging pipelines, and failed builds. ## Core Features & Use Cases - Deployment Command Guidance: Covers vercel deploy, vercel --prod, vercel build, vercel deploy --prebuilt, vercel promote, vercel rollback, and vercel inspect with clear explanations of when to use each. - CI/CD Pipeline Templates: Ready-to-use workflow configurations for GitHub Actions, GitLab CI, and Bitbucket Pipelines, including required environment variables (VERCEL_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID). - Advanced Patterns: Preview deployments on pull requests, promote-after-tests workflows, OIDC federation for runtime backend access, and a deployment strategy matrix for monorepos and atomic deploys. - Use Case: You want every pull request to produce a preview URL posted as a PR comment, then automatically promote to production after E2E tests pass on main. This Skill provides the exact GitHub Actions YAML and CLI commands to implement it. ## Quick Start Ask the assistant to generate a GitHub Actions workflow that builds and deploys your project to Vercel production using the prebuilt deployment pattern.
