Deployments Cicd
Wire Vercel preview and production deploys, promotions, rollbacks, and CI workflow files without guessing platform-native patterns.
Overview
Deployments-cicd is an agent skill for the Ship phase that guides Vercel deployment, promotion, rollback, inspection, prebuilt builds, and CI workflow configuration.
Install
npx skills add https://github.com/vercel/vercel-plugin --skill deployments-cicdWhat is this skill?
- Guides vercel deploy, --prod, promote, rollback, inspect, and build --prebuilt from official docs patterns
- Maps triggers to repo paths: .github/workflows, vercel.json, GitLab/Bitbucket CI files
- Recommends Vercel Cron Jobs in vercel.json instead of ad-hoc node-cron in app code
- Covers Git-linked preview deployments and promoting a preview to production
- Retrieval aliases for deploy, CI/CD, rollback, and continuous deployment intents
- Validate rule flags manual cron scheduling and recommends vercel.json crons
- Path patterns cover GitHub, GitLab, Bitbucket CI and vercel.json layouts
Adoption & trust: 516 installs on skills.sh; 186 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a Vercel project and CI files but are unsure how to deploy safely, promote previews, roll back, or avoid non-native cron patterns.
Who is it for?
Solo builders shipping on Vercel who touch GitHub Actions, vercel.json, or vercel CLI promote/rollback flows.
Skip if: Teams on non-Vercel hosts only, or apps with no deployment or CI configuration in the repo.
When should I use this skill?
Deploying, promoting, rolling back, or inspecting Vercel deployments; configuring CI workflow files; building with --prebuilt.
What do I get? / Deliverables
You get stepwise Vercel-aligned deploy and CI/CD actions and validate rules that match vercel.json and workflow file conventions.
- CI workflow or vercel.json changes aligned with Vercel deployment docs
- Documented deploy, promote, or rollback steps for the agent to execute
Recommended Skills
Journey fit
Deployment and release pipelines sit in Ship when you move from built code to environments users can hit. Launch subphase covers production promotion, preview URLs, and CI gates that gate going live on Vercel.
How it compares
Platform deployment playbook for Vercel—not a generic Docker or Kubernetes ship skill.
Common Questions / FAQ
Who is deployments-cicd for?
Indie and solo developers using Vercel who want an agent to reason about deploy commands, previews, production promotion, and CI YAML without contradicting Vercel docs.
When should I use deployments-cicd?
Use it during Ship when you deploy to Vercel, set up continuous deployment, promote or rollback a deployment, inspect a build, use vercel build --prebuilt, or edit .github/workflows and vercel.json for release pipelines.
Is deployments-cicd safe to install?
Review the Security Audits panel on this Prism page and treat any skill that suggests shell and Git changes as something you verify in your own repo before merging.
SKILL.md
READMESKILL.md - Deployments Cicd
# Vercel Deployments & CI/CD You are an expert in Vercel deployment workflows — `vercel deploy`, `vercel promote`, `vercel rollback`, `vercel inspect`, `vercel build`, and CI/CD pipeline integration with GitHub Actions, GitLab CI, and Bitbucket Pipelines. ## Deployment Commands ### Preview Deployment ```bash # Deploy from project root (creates preview URL) vercel # Equivalent explicit form vercel deploy ``` Preview deployments are created automatically for every push to a non-production branch when using Git integration. They provide a unique URL for testing. ### Production Deployment ```bash # Deploy directly to production vercel --prod vercel deploy --prod # Force a new deployment (skip cache) vercel --prod --force ``` ### Build Locally, Deploy Build Output ```bash # Build locally (uses development env vars by default) vercel build # Build with production env vars vercel build --prod # Deploy only the build output (no remote build) vercel deploy --prebuilt vercel deploy --prebuilt --prod ``` **When to use `--prebuilt`:** Custom CI pipelines where you control the build step, need build caching at the CI level, or need to run tests between build and deploy. ### Promote & Rollback ```bash # Promote a preview deployment to production vercel promote <deployment-url-or-id> # Rollback to the previous production deployment vercel rollback # Rollback to a specific deployment vercel rollback <deployment-url-or-id> ``` **Promote vs deploy --prod:** `promote` is instant — it re-points the production alias without rebuilding. Use it when a preview deployment has been validated and is ready for production. ### Inspect Deployments ```bash # View deployment details (build info, functions, metadata) vercel inspect <deployment-url> # List recent deployments vercel ls # View logs for a deployment vercel logs <deployment-url> vercel logs <deployment-url> --follow ``` ## CI/CD Integration ### Required Environment Variables Every CI pipeline needs these three variables: ```bash VERCEL_TOKEN=<your-token> # Personal or team token VERCEL_ORG_ID=<org-id> # From .vercel/project.json VERCEL_PROJECT_ID=<project-id> # From .vercel/project.json ``` Set these as secrets in your CI provider. Never commit them to source control. ### GitHub Actions ```yaml name: Deploy to Vercel on: push: branches: [main] jobs: deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Install Vercel CLI run: npm install -g vercel - name: Pull Vercel Environment run: ve