Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
Deployment principles and decision-making for safe production releases. Learn to THINK, not memorize scripts.
This skill teaches deployment principles, not bash scripts to copy.
What are you deploying?
│
├── Static site / JAMstack
│ └── Vercel, Netlify, Cloudflare Pages
│
├── Simple web app
│ ├── Managed → Railway, Render, Fly.io
│ └── Control → VPS + PM2/Docker
│
├── Microservices
│ └── Container orchestration
│
└── Serverless
└── Edge functions, Lambda
| Platform | Deployment Method | |----------|------------------| | Vercel/Netlify | Git push, auto-deploy | | Railway/Render | Git push or CLI | | VPS + PM2 | SSH + manual steps | | Docker | Image push + orchestration | | Kubernetes | kubectl apply |
| Category | What to Check | |----------|--------------| | Code Quality | Tests passing, linting clean, reviewed | | Build | Production build works, no warnings | | Environment | Env vars set, secrets current | | Safety | Backup done, rollback plan ready |
1. PREPARE
└── Verify code, build, env vars
2. BACKUP
└── Save current state before changing
3. DEPLOY
└── Execute with monitoring open
4. VERIFY
└── Health check, logs, key flows
5. CONFIRM or ROLLBACK
└── All good? Confirm. Issues? Rollback.
| Phase | Principle | |-------|-----------| | Prepare | Never deploy untested code | | Backup | Can't rollback without backup | | Deploy | Watch it happen, don't walk away | | Verify | Trust but verify | | Confirm | Have rollback trigger ready |
| Check | Why | |-------|-----| | Health endpoint | Service is running | | Error logs | No new errors | | Key user flows | Critical features work | | Performance | Response times acceptable |
| Symptom | Action | |---------|--------| | Service down | Rollback immediately | | Critical errors | Rollback | | Performance >50% degraded | Consider rollback | | Minor issues | Fix forward if quick |
| Platform | Rollback Method | |----------|----------------| | Vercel/Netlify | Redeploy previous commit | | Railway/Render | Rollback in dashboard | | VPS + PM2 | Restore backup, restart | | Docker | Previous image tag | | K8s | kubectl rollout undo |
| Strategy | How It Works | |----------|--------------| | Rolling | Replace instances one by one | | Blue-Green | Switch traffic between environments | | Canary | Gradual traffic shift |
| Scenario | Strategy | |----------|----------| | Standard release | Rolling | | High-risk change | Blue-green (easy rollback) | | Need validation | Canary (test with real traffic) |
| Check | Common Issues | |-------|--------------| | Logs | Errors, exceptions | | Resources | Disk full, memory | | Network | DNS, firewall | | Dependencies | Database, APIs |
| ❌ Don't | ✅ Do | |----------|-------| | Deploy on Friday | Deploy early in week | | Rush deployment | Follow the process | | Skip staging | Always test first | | Deploy without backup | Backup before deploy | | Walk away after deploy | Monitor for 15+ min | | Multiple changes at once | One change at a time |
Before deploying:
Remember: Every deployment is a risk. Minimize risk through preparation, not speed.
npx skills add davila7/deployment-procedures下载完整 Skill 目录，包含 SKILL.md 及所有相关文件
Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
Gemini CLI for one-shot Q&A, summaries, and generation.
Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with the npm-installed clawhub CLI.
Capture and automate macOS UI with the Peekaboo CLI.
Category:developer