agentleFS
alex-voloshin-devalex-voloshin-dev/ai-skills/.agents/skills/deployment-procedures/SKILL.md

deployment-procedures

Skill2 starsChanged 6 months agoMITView on GitHub

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.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use intelligent-routing, nextjs-react-expert and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SKB3002Skill

    intelligent-routing

    Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.

    Also in 6 projects that use this

  • SKB3002Skill

    nextjs-react-expert

    React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.

    Also in 3 projects that use this

  • xfstudioSkill

    rust-pro

    Master Rust 1.75+ with modern async patterns, advanced type system

    Also in 5 projects that use this

  • goca-seSkill

    batch-operations

    Apply a change safely across many files — refactors touching more than 5 files, library or API migrations, project-wide renames of symbols/imports/paths, or adding boilerplate to many files. Use when "do it all at once" risks context overflow or silent failures.

    Also in 3 projects that use this

  • jornalistainclusivoSkill

    design-spec

    How to author a DESIGN.md file — the machine-readable design-token + human-rationale format that must exist before any UI is built. YAML front-matter token schema (colors, typography, spacing, rounded, components), type system, token references, and canonical section order.

    Also in 3 projects that use this

  • sefaertuncSkill

    coordinator-mode

    Multi-agent orchestration patterns: when to use coordinator mode, worker prompts, parallel execution

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If healthy → gradually increase traffic (25% → 50% → 100%)

    line 47
  2. Distinctive:

    If degraded → route all traffic back to stable version

    line 48
  3. Distinctive:

    Run full smoke tests against green

    line 53
  4. Distinctive:

    Keep blue running for instant rollback (15–30 minutes)

    line 55

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

StrategyWhen to UseRiskDowntime
Rolling updateStandard deploys, stateless servicesLowZero
Blue-GreenCritical services, instant rollback neededLowZero
CanaryHigh-risk changes, gradual validationMediumZero
RecreateStateful services, breaking schema changesHighBrief

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

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

Blue-Green Deployment

  1. Deploy new version alongside current (green alongside blue)
  2. Run full smoke tests against green
  3. Switch traffic from blue to green
  4. Keep blue running for instant rollback (15–30 minutes)
  5. 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.