Deployment procedures

Skill alex-voloshin-dev/ai-skills/.agents/skills/deployment-procedures

Production deployment procedures with rollback plans, health checks, and verification steps. Use when deploying to production, planning rollback strategies, or verifying production health after deployment.From its SKILL.md

Install

npx -y skills add alex-voloshin-dev/ai-skills --skill deployment-procedures

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.9 KB, as published. Nobody here has run it

Deploy to Production

Production deployment skill providing rollback procedures, health check patterns, and verification checklists. Ensures safe, repeatable production deployments.

When to Use

Deploying application updates to production
Planning rollback strategies before deployment
Verifying production health after deployment
Investigating post-deployment issues

When NOT to Use

Deploying to staging (use deploy-staging skill workflow)
Making infrastructure changes (use infra-change skill workflow)
Planning release version and changelog (use release skill workflow)

Deployment Strategies

Strategy	When to Use	Risk	Downtime
Rolling update	Standard deploys, stateless services	Low	Zero
Blue-Green	Critical services, instant rollback needed	Low	Zero
Canary	High-risk changes, gradual validation	Medium	Zero
Recreate	Stateful services, breaking schema changes	High	Brief

Rolling Update (Default)

Gradually replace old pods with new ones
Health checks gate the rollout — unhealthy pods stop the rollout
Configure maxSurge and maxUnavailable for rollout speed
Monitor error rates during rollout window

Canary Deployment

Deploy new version to small subset (5–10% traffic)
Monitor error rate, latency, and business metrics for 5–10 minutes
If healthy → gradually increase traffic (25% → 50% → 100%)
If degraded → route all traffic back to stable version

Blue-Green Deployment

Deploy new version alongside current (green alongside blue)
Run full smoke tests against green
Switch traffic from blue to green
Keep blue running for instant rollback (15–30 minutes)
Decommission blue after confidence period

Pre-Deployment Checklist

All tests pass on release branch
Staging deployment verified
Database migrations tested (forward and rollback)
Feature flags configured
Monitoring dashboards ready
On-call team notified
Rollback plan documented and tested
Release notes prepared

Post-Deployment Verification

Health endpoint returns 200
Error rate ≤ pre-deploy baseline
Latency P95 within SLO target
No new error patterns in logs
Key user journeys functional
Database connections stable
External integrations responding
Alerts not firing

Integration

Follows rules: devops-engineer role (infrastructure), sre-engineer role (SLOs, monitoring)
Used by workflows: deploy-production skill, deploy-staging skill
Companion resources: rollback-procedure.md

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.