Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

deployment

Estrellas2

Forks0

Actualizado14 de febrero de 2026 a las 05:09

Plan and execute safe deployments with rollback procedures, verification, and monitoring

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

jerdaw

jerdaw/agentic-best-practices

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Administradores de redes y sistemas informáticosOcupaciones informáticas y matemáticas·SOC 15-1244

SKILL.md

readonly

name	deployment
description	Plan and execute safe deployments with rollback procedures, verification, and monitoring

Deployment

Plan and execute safe deployments — rollback procedures, verification steps, and monitoring.

When to Use

Preparing a production deployment
Setting up deployment pipelines
Defining rollback procedures
Verifying a deployment post-release

Workflow

1. Pre-Deployment Checklist

Before deploying:

2. Choose a Deployment Strategy

Strategy	When	Risk
Blue/Green	Need instant rollback	Low — traffic switch
Canary	Testing with real traffic	Low — limited blast radius
Rolling	Resource-constrained environments	Medium — gradual exposure
Direct	Non-critical services only	High — all-or-nothing

3. Deploy

# Example: Kubernetes blue/green
kubectl apply -f deployment-green.yaml
kubectl rollout status deployment/myapp-green

# Verify health
curl -f https://myapp-green.internal/health/ready

# Cut traffic
kubectl patch service myapp -p '{"spec":{"selector":{"version":"green"}}}'

4. Post-Deployment Verification

Health check — /health/ready returns 200
Smoke test — Critical user path works (e.g., login)
Metrics — Error rate and latency within normal range
Logs — No new error patterns in aggregator

5. Rollback (if needed)

Trigger	Action
Error rate > 1% for 5 minutes	Automated rollback to N-1
Performance degradation > 50%	Manual rollback after investigation
Security vulnerability found	Emergency rollback immediately

# Blue/Green rollback — switch selector back
kubectl patch service myapp -p '{"spec":{"selector":{"version":"blue"}}}'

6. Post-Deploy

Confirm metrics stable for 30 minutes
Update deployment log/changelog
Communicate to team

Red Flags

Signal	Action
Friday afternoon deploy	Postpone to Monday
No rollback plan	Define triggers and procedure first
Skipping staging	Run in staging first
100% traffic on first deploy	Use canary or blue/green

Related Skills

Skill	When
e2e-testing	Smoke testing after deploy
secure-coding	Security review before release
logging	Verifying logs post-deploy

Backing Guide

Deployment Strategies

Más de este repositorio

mismo repositorio

git-workflow

jerdaw/agentic-best-practices

Execute safe Git workflows — branching, committing, resolving conflicts, and managing PRs

2026-06-052

cost-management

jerdaw/agentic-best-practices

Use when controlling AI spend, token budgets, model routing, or workflow efficiency before scaling usage

2026-04-212

incident-response

jerdaw/agentic-best-practices

Use when handling incidents, outages, severe regressions, or operational emergencies before attempting broad fixes

2026-04-212

performance

jerdaw/agentic-best-practices

Use when investigating latency, throughput, resource saturation, or performance regressions before changing implementation details

2026-04-212

code-review

jerdaw/agentic-best-practices

Use when reviewing code, preparing a PR for review, or processing review feedback

2026-02-142

debugging

jerdaw/agentic-best-practices

Use when diagnosing bugs, test failures, or unexpected behavior before attempting any fix

2026-02-142

name	deployment
description	Plan and execute safe deployments with rollback procedures, verification, and monitoring

Deployment

Plan and execute safe deployments — rollback procedures, verification steps, and monitoring.

When to Use

Preparing a production deployment
Setting up deployment pipelines
Defining rollback procedures
Verifying a deployment post-release

Workflow

1. Pre-Deployment Checklist

Before deploying:

2. Choose a Deployment Strategy

Strategy	When	Risk
Blue/Green	Need instant rollback	Low — traffic switch
Canary	Testing with real traffic	Low — limited blast radius
Rolling	Resource-constrained environments	Medium — gradual exposure
Direct	Non-critical services only	High — all-or-nothing

3. Deploy

# Example: Kubernetes blue/green
kubectl apply -f deployment-green.yaml
kubectl rollout status deployment/myapp-green

# Verify health
curl -f https://myapp-green.internal/health/ready

# Cut traffic
kubectl patch service myapp -p '{"spec":{"selector":{"version":"green"}}}'

4. Post-Deployment Verification

Health check — /health/ready returns 200
Smoke test — Critical user path works (e.g., login)
Metrics — Error rate and latency within normal range
Logs — No new error patterns in aggregator

5. Rollback (if needed)

Trigger	Action
Error rate > 1% for 5 minutes	Automated rollback to N-1
Performance degradation > 50%	Manual rollback after investigation
Security vulnerability found	Emergency rollback immediately

# Blue/Green rollback — switch selector back
kubectl patch service myapp -p '{"spec":{"selector":{"version":"blue"}}}'

6. Post-Deploy

Confirm metrics stable for 30 minutes
Update deployment log/changelog
Communicate to team

Red Flags

Signal	Action
Friday afternoon deploy	Postpone to Monday
No rollback plan	Define triggers and procedure first
Skipping staging	Run in staging first
100% traffic on first deploy	Use canary or blue/green

Related Skills

Skill	When
e2e-testing	Smoke testing after deploy
secure-coding	Security review before release
logging	Verifying logs post-deploy

Backing Guide

Deployment Strategies