<< All versions
Skill v1.0.1
currentAutomated scan100/100zhaono1/agent-playbook/deployment-engineer
+7 new
──Details
PublishedJuly 13, 2026 at 08:11 PM
Content Hashsha256:5170fec6492b058b...
Git SHAc79bd5fcff09
Bump Typepatch
──Files
Files (1 file, 5.2 KB)
SKILL.md5.2 KBactive
SKILL.md · 250 lines · 5.2 KB
version: "1.0.1" name: deployment-engineer description: Deployment automation specialist for CI/CD pipelines and infrastructure. Use when setting up deployment, configuring CI/CD, or managing releases. allowed-tools: Read, Write, Edit, Bash, Grep, Glob metadata: hooks: after_complete:
- trigger: session-logger
mode: auto reason: "Log deployment activity"
Deployment Engineer
Specialist in deployment automation, CI/CD pipelines, and infrastructure management.
When This Skill Activates
Activates when you:
- Set up deployment pipeline
- Configure CI/CD
- Manage releases
- Automate infrastructure
CI/CD Pipeline
Pipeline Stages
yaml
stages:- lint- test- build- security- deploy-dev- deploy-staging- deploy-production
GitHub Actions Example
yaml
name: CI/CDon:push:branches: [main, develop]pull_request:branches: [main]jobs:lint:runs-on: ubuntu-lateststeps:- uses: actions/checkout@v4- uses: actions/setup-node@v4with:node-version: '20'- run: npm ci- run: npm run linttest:runs-on: ubuntu-latestneeds: lintsteps:- uses: actions/checkout@v4- uses: actions/setup-node@v4- run: npm ci- run: npm testbuild:runs-on: ubuntu-latestneeds: teststeps:- uses: actions/checkout@v4- uses: actions/setup-node@v4- run: npm ci- run: npm run build- uses: actions/upload-artifact@v4with:name: buildpath: dist/deploy-production:runs-on: ubuntu-latestneeds: buildif: github.ref == 'refs/heads/main'environment: productionsteps:- uses: actions/checkout@v4- uses: actions/download-artifact@v4with:name: buildpath: dist/- run: npm run deploy
Deployment Strategies
1. Blue-Green Deployment
┌─────────┐│ Load ││ Balancer│└────┬────┘│┌────────┴────────┐│ Switch │├────────┬────────┤▼ ▼ ▼┌─────┐ ┌─────┐ ┌─────┐│Blue │ │Green│ │ │└─────┘ └─────┘ └─────┘
2. Rolling Deployment
┌─────────────────────────────────────┐│ v1 v1 v1 v1 v1 v1 v1 v1 v1 │ → Old│ v2 v2 v2 v2 v2 v2 v2 v2 v2 │ → New└─────────────────────────────────────┘▲ ▲│ │Start End
3. Canary Deployment
┌──────────────────────────────────────┐│ v1 v1 v1 v1 v1 v1 v1 v1 v1 v1 │ → Old│ v2 v2 v2 v2 │ → Canary (5%)└──────────────────────────────────────┘Monitor metrics, then:│ v1 v1 v1 v1 │ → Old (50%)│ v2 v2 v2 v2 v2 v2 v2 v2 v2 v2 │ → New (50%)
Environment Configuration
Environment Variables
bash
# ProductionNODE_ENV=productionDATABASE_URL=postgresql://...API_KEY=${API_KEY}SENTRY_DSN=https://example.com/123# DevelopmentNODE_ENV=developmentDATABASE_URL=postgresql://localhost:5432/dev
Configuration Management
typescript
// config/production.tsexport default {database: {url: process.env.DATABASE_URL,poolSize: 20,},redis: {url: process.env.REDIS_URL,},};
Health Checks
typescript
// GET /healthapp.get('/health', (req, res) => {const health = {status: 'ok',timestamp: new Date().toISOString(),checks: {database: 'ok',redis: 'ok',external_api: 'ok',},};if (Object.values(health.checks).some(v => v !== 'ok')) {health.status = 'degraded';return res.status(503).json(health);}res.json(health);});
Rollback Strategy
bash
# Kuberneteskubectl rollout undo deployment/app# Dockerdocker-compose downdocker-compose up -d --scale app=<previous-version># Gitgit revert HEADgit push
Monitoring & Logging
Metrics to Track
- Deployment frequency
- Lead time for changes
- Mean time to recovery (MTTR)
- Change failure rate
Logging
typescript
// Structured logginglogger.info('Deployment started', {version: process.env.VERSION,environment: process.env.NODE_ENV,timestamp: new Date().toISOString(),});
Scripts
Generate deployment config:
bash
python scripts/generate_deploy.py <environment>
Validate deployment:
bash
python scripts/validate_deploy.py
References
references/pipelines.md- CI/CD pipeline examplesreferences/kubernetes.md- K8s deployment configsreferences/monitoring.md- Monitoring setup