Results for “rollout”

Deploy an entire redesigned site to AEM Edge Delivery Services by inventorying migrated pages, deduplicating blocks, and driving per-page deployment with tracking and verification.

`task-agent`/`review-agent`: use when a Kubernetes workload, route, identity, health, capacity, or rollout boundary changes; skip image-only, pipeline-only, and non-cluster work.

Prepare and verify a staged or production deployment with rollback and smoke checks.

The relevant axis is not "how do we deploy" but "how fast and how cheaply can we

Provides a structured pre-launch checklist, staged rollout plan, monitoring setup, and rollback strategy for safe production deployments.

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.

Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

Composite skill — promote the long-lived `release` branch to `main`, cut a single version that batches every PR accumulated since the last tag, then clean up. Chains pr-merge-readiness (on release→main PR) → version-bump (semver from commits) → changelog-update (promote [Unreleased] → versioned) → ship (tag + GitHub release) → stale-branch cleanup → optional ship-it for deploy. Use this INSTEAD of releasing every small fix individually. Many small commits become one well-scoped release.

Delegates a bounded repository task to an allowlisted external coding CLI through a guarded runner, with provider selection, timeout handling, and independent local review.

Identify, test, deploy, and verify software updates across an organization's IT infrastructure using a structured patch management workflow with phased rollouts and automated assessment.

Guides reliable application deployment with CI/CD pipelines, zero-downtime strategies, rollback plans, and post-deploy monitoring.

`analysis-agent`/`task-agent`/`review-agent`: use for release identity, compatibility, exposure, stop, rollback, or recovery; skip pipeline-only and no-release work.

Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "timeout strategy", "deployment pipeline", "chaos engineering", "bulkhead pattern", "retry with backoff", or "health checks". Also trigger when designing resilient microservices, planning zero-downtime deployments, or investigating cascading failure scenarios. Covers capacity planning, health checks, and anti-fragility patterns. For data systems, see ddia-systems. For system architecture, see system-design.

Full release pipeline — tests → coverage → review gate → version bump → CHANGELOG → commit → PR

Plan and execute migrations from Zscaler, Palo Alto, legacy VPN, or SASE stacks to Cloudflare One with policy mapping, rollout plans, and parity analysis.

Prevent Kubernetes hallucinations by diagnosing and fixing failure modes: insecure workload defaults, resource starvation, network exposure, privilege sprawl, fragile rollouts, and API drift. Use when generating, reviewing, refactoring, or migrating manifests, Helm charts, Kustomize overlays, cluster policies, and platform-specific Kubernetes work for EKS, GKE, AKS, OpenShift, GitOps controllers, or observability stacks.