syahiidkamil/Software-Engineer-AI-Agent-Atlas / .claude/skills/deploy
deploy
FlaggedTake 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.8 KB |
| providers/coolify.md | markdown | 2.3 KB |
| providers/docker-compose-ssh.md | markdown | 1.2 KB |
| providers/fly.md | markdown | 1.2 KB |
| providers/netlify.md | markdown | 1.1 KB |
| providers/railway.md | markdown | 950 B |
| providers/vercel.md | markdown | 1.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'`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |