bkinsey808/deployment-operations

Requires: file-read, terminal (Wrangler/Cloudflare CLI). No network access needed.

Deployment Operations Skill

Use When

Use this skill when:

• Handling production incidents, rollback decisions, or post-deploy checks.
• Diagnosing runtime issues immediately after deployment.

Execution workflow:

1. Prioritize safe recovery (rollback/mitigation) before deep root-cause changes.
2. Validate system health with existing health checks and logs.
3. Document exact operational commands/actions taken.
4. After stabilization, identify follow-up fixes to prevent recurrence.

Output requirements:

• Report incident scope, recovery path used, and current health status.
• Include exact rollback/verification commands used.

What This Skill Does

• Rollback — fast recovery when a deployment breaks production
• Health checks — verifying the API and frontend are running correctly
• Troubleshooting — diagnosing the most common post-deploy problems

---

Rollback Procedures

Rollback via Git Revert (recommended)

# Revert the last commit and push — GitHub Actions auto-deploys the reversion
git revert HEAD
git push origin main
# Wait ~2 minutes for deployment

Manual Rollback (faster if CI is slow)

# Build and deploy the previous commit directly
git checkout main~1
npm run build:all
npm run deploy:production

# Reset HEAD back to current state
git checkout main

API-Only Rollback (if only the Worker broke)

wrangler rollback --env production

Verify Rollback Succeeded

npm run health:check
curl https://<your-domain>/api/health
wrangler tail --env production

---

Monitoring & Health Checks

Health Check Endpoint

curl https://<your-domain>/api/health
# Expected: { "status": "ok", "environment": "production", "timestamp": "..." }

npm run health:check   # automated — checks API, frontend, DB, realtime
npm run status:deployment
wrangler tail --env production   # live log stream

Cloudflare Analytics

Go to Analytics → Traffic in the Cloudflare dashboard to check for 5xx error spikes or response time regressions after deploy.

---

Troubleshooting

Users Still See Old Version After Deploy

# 1. Try hard refresh in browser (Ctrl+Shift+R) — if that works, it's a cache issue
# 2. Open incognito window — if that works, it's browser cache only

npm run cache:purge         # purge Cloudflare CDN
npm run status:deployment   # confirm correct commit is deployed

If still broken after 5 minutes, manually purge in the Cloudflare dashboard: Caching → Purge Cache → Purge Everything.

Deployment Hangs or Times Out

# Reproduce locally
npm run build:all

# Check Node version (must be 20+)
node --version

# Clear build cache and retry
npm run clean
npm run build:all

Then check wrangler tail --env production for runtime startup errors.

Environment Variables Not Working

# List what's deployed
wrangler secret list --env production

# If missing, set and redeploy
wrangler secret put KEY_NAME --env production
npm run deploy

---

References

• docs/devops/deploy.md
• Core deploy workflow: deployment-strategies skill
• Cache + CI/CD: cloudflare-cache-cicd skill

Do Not

• Do not violate repo-wide rules in docs/ai/rules.md.
• Do not add broad lint/type suppressions without explicit justification.
• Do not expand scope beyond the requested task without calling it out.

Success Criteria

• Changes follow this skill's conventions and project rules.
• Relevant validation commands are run, or skipped with a clear reason.
• Results clearly summarize behavior impact and remaining risks.

Skill Handoffs

• If modifying deployment configuration/workflows, also load deployment-strategies.
• If cache invalidation or CI cache behavior is involved, also load cloudflare-cache-cicd.