vercel-deploy

name	vercel-deploy
description	Run Vercel-specific deployment operations for linked web/fullstack projects: preview deploys, direct production deploys, staged deploy + promote flows, aliases/domains, environment-variable sync, and rollback response. Use when the request is specifically about operating a project on Vercel after the provider is already chosen — especially when someone needs a preview URL, stable alias, custom domain, env-scope fix, production cutover, or rollback on Vercel. Triggers on: Vercel deploy, Vercel preview URL, vercel promote, vercel alias, Vercel domain, Vercel env, Vercel rollback, and Vercel CLI deployment. Route provider-neutral release strategy to `deployment-automation`, CI/workflow authoring to `workflow-automation`, and local install/auth/bootstrap work to `system-environment-setup`.
allowed-tools	Bash Read Write Edit Glob Grep
compatibility	Best when a repository already targets Vercel and either has the Vercel CLI available or can follow dashboard-backed Vercel workflows. Assumes the agent can inspect repo config and run Vercel commands if authenticated.
license	MIT
metadata	{"tags":"vercel, deployment, preview, production, promote, alias, domains, environment-variables, rollback","platforms":"Claude, ChatGPT, Gemini, Codex","version":"2.1.0","modernization":"2026-04-15T00:00:00.000Z","structural_hardening":"2026-04-18T00:00:00.000Z","source":"akillness/oh-my-skills"}

Vercel Deploy

Use this skill when the job is operating a deployment on Vercel specifically, not designing generic rollout policy.

vercel-deploy is the provider-specific front door for:

• creating or refreshing Vercel preview deployments
• running a direct production deployment on Vercel
• staging a deploy, verifying it, then promoting it live
• assigning a stable preview alias or attaching a custom domain
• inspecting/fixing Vercel environment-variable scope and redeploy needs
• responding to a bad production deployment with rollback-oriented checks

Read these support docs before choosing the mode:

• references/modes-and-boundaries.md
• references/preview-production-command-packets.md
• references/env-domain-rollback-troubleshooting.md

When to use this skill

• The user explicitly wants to deploy a project on Vercel
• The job is about a Vercel preview URL, preview alias, or stable demo environment
• A linked Vercel deployment already exists and needs promotion or rollback handling
• The main issue is Vercel env scope, Vercel domain/alias state, or Vercel-specific release verification
• The provider has already been chosen and the user needs Vercel operator guidance rather than vendor-neutral release design

When not to use this skill

• The main question is generic rollout strategy, release gating, canary policy, or cross-provider deployment design → use deployment-automation
• The main job is editing GitHub Actions / CI YAML / task runners around the deploy flow → use workflow-automation
• The main job is installing Node, Vercel CLI, auth bootstrap, or linking the local machine → use system-environment-setup
• The app/framework/build is broken before the deploy path itself works → use debugging or the relevant framework/build skill first
• The main job is long-lived telemetry, SLOs, or alerting after release → use monitoring-observability

Instructions

Step 1: Normalize the Vercel job into one packet

Choose exactly one primary mode before reaching for commands.