Skip to content

syahiidkamil/Software-Engineer-AI-Agent-Atlas / .claude/skills/deploy

deploy

Flagged

Take a project from working locally to running in production, provider-agnostic — write the DEPLOY.md runbook, gate a release, deploy through the existing CI/CD pipeline, the provider's CLI or API, or exact printed steps, then health-check, smoke-test, and log it. Use when deploying, shipping, releasing, setting up hosting, rolling back, or reading production logs.

FileKindSize
SKILL.mdskill md7.8 KB
providers/coolify.mdmarkdown2.3 KB
providers/docker-compose-ssh.mdmarkdown1.2 KB
providers/fly.mdmarkdown1.2 KB
providers/netlify.mdmarkdown1.1 KB
providers/railway.mdmarkdown950 B
providers/vercel.mdmarkdown1.4 KB

providers/vercel.md

View on GitHub
# Vercel

Install: `npm i -g vercel`. Checked 2026-11; verify with `vercel --help`.

## Token
`VERCEL_TOKEN` (account settings -> Tokens; scope it to the team, set an expiry), plus
`VERCEL_ORG_ID` and `VERCEL_PROJECT_ID` from `.vercel/project.json` after `vercel link`.
The user stores it: `node .claude/scripts/secrets.cjs set VERCEL_TOKEN`. The CLI reads `VERCEL_TOKEN`
from its environment, so `secrets.cjs run` is enough.

## Deploy
Production (prebuilt, reproducible):
```
node .claude/scripts/secrets.cjs run <project> --env prod -- vercel pull --yes --environment=production
node .claude/scripts/secrets.cjs run <project> --env prod -- vercel build --prod
node .claude/scripts/secrets.cjs run <project> --env prod -- vercel deploy --prebuilt --prod
```
Preview: the same with `--environment=preview` and without `--prod`.

## Logs
`vercel logs --environment production --since 1h` (CLI v64 removed streaming `--follow` and the
positional deployment argument); build logs: `vercel inspect <url> --logs`.

## Rollback
`vercel rollback [deployment-url-or-id]`; undo with `vercel promote <id>`. Hobby plans can only
roll back to the previous production deployment.

## Env vars on the platform
`vercel env add NAME production --sensitive` reads the value from stdin: the user runs it, or pipe
it from the store with `secrets.cjs run ... -- sh -c 'printf %s "$NAME" | vercel env add NAME production --sensitive'`.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall