Vercel Deploy Assistant
Seleccionado

Vercel Deploy Assistant

One-click Vercel deployments, preview rollbacks, and production monitoring with automated CI/CD workflows.

3 habilidades 0 instalaciones
verceldeploycicdpreviewrollback
Actualizado hace 3 dias

Instalar

Ejecuta este comando para instalar todas las habilidades en este complemento:

npx skillstore add @vercel-deploy-assistant

Las habilidades se instalarán en el directorio .claude/skills/

Descripcion general

Guia de uso

Mejorado por IA

Guia detallada

## Who Is This For

Frontend developers and indie hackers deploying Next.js apps to Vercel. This plugin handles the full deploy lifecycle — from applying best practices and managing env vars to triggering deployments and monitoring status — all from chat.

## 3-Step Quickstart

1. **Review before you ship** — ask: `"Use next-best-practices to review my Next.js app structure and flag any issues before deploying"`. The skill checks Server Components usage, data fetching patterns, and file conventions.
2. **Deploy** — ask: `"Use vercel-deployment to deploy my project at ~/Projects/myapp to production"`. The skill handles the Vercel CLI flow including env var validation.
3. **Manage the deployment** — ask: `"Use vercel-automation to list my last 5 deployments and show the status of each"`. The skill can also roll back, manage DNS, or update environment variables.

## Step → Skill → Input → Output

| Step | Skill | What You Provide | What You Get |
|------|-------|------------------|--------------|
| Pre-deploy review | next-best-practices | Project directory or code snippet | Issues list + best practice recommendations |
| Deploy | vercel-deployment | Project path + target environment | Deploy URL + build log summary |
| Post-deploy management | vercel-automation | Project name + action (list/rollback/dns) | Deployment list, status, or confirmation |

## Common Failures & Fixes

- **vercel-deployment fails with "not logged in"** → Run `vercel login` in your terminal first, or provide a `VERCEL_TOKEN` env var.
- **next-best-practices flags Server Component issues** → Follow the fix suggestions in the output. Common fix: move `"use client"` to the smallest possible subtree.
- **vercel-automation can't find the project** → Project names are case-sensitive in Vercel. Check the exact name in your Vercel dashboard.

## Success Criteria

You know it worked when:
- next-best-practices returns a checklist with all critical items green
- vercel-deployment returns a live `.vercel.app` URL
- vercel-automation lists your deployments with accurate timestamps and status

Habilidades

3