Define post-deploy health checks, canary monitoring, and rollback workflows.
npx skills add https://github.com/PiercingXX/xx-stack --skill ops-deploy-land
Please help me install this Agent Skill. Skill: ops-deploy-land Source: https://github.com/PiercingXX/xx-stack/tree/main/runtime/skills/ops-deploy-land Command: npx skills add https://github.com/PiercingXX/xx-stack --skill ops-deploy-land
This Skill reduces the risk of bad production releases by guiding you through post-deploy health verification, canary monitoring, and a controlled rollback plan within the first critical minutes.
Use case: You just merged changes to production and need to confirm the deployment is healthy quickly, catch regressions early with canary metrics, and execute rollback if KPIs degrade.
Instruct the AI to perform post-deployment operations for the last release by checking the repo’s available health/telemetry surfaces, running a 30-minute KPI verification plan, and producing a deployment report plus a rollback decision outline.
High-intent search queries and answers about installing and using this skill.
Verify production deployments by running a 30-minute KPI check covering error rates, latency, login success, and database performance. This immediate post-deploy health verification catches regressions early by gating on metric-driven thresholds to detect spikes.
Rollback during a canary deployment should trigger when explicit decision rules detect degraded KPIs like error rate spikes or latency increases. Monitoring gradual traffic rollouts from 5% to 100% requires metric-driven gating to catch these failures.
Incident response for a bad release produces a structured reporting output focused on the first 30 minutes and 24-hour follow-up. It executes controlled rollback procedures and verifies system health after the rollback to stabilize production.
Canary monitoring can be approximated with release-readiness checks if your infrastructure lacks a native traffic rollout mechanism. The workflow adapts to available telemetry surfaces to validate KPIs even without explicit canary deployment controls.
The best way to structure a post-deploy health check workflow is to define explicit decision rules for rollback and metric-driven gating for errors and latency. This ensures release promotions are validated against immediate KPI thresholds.
haxlysConfigure Istio VirtualService, DestinationRule, Gateway, and ServiceEntry for service mesh routing.
LuminairPrimeGenerate structured Markdown runbook skeletons for microservices and platform services.
kubiyabotQuery Datadog metrics, manage monitors, and post events via dogshell CLI.
rohitg00Automate progressive Kubernetes deployments with Argo Rollouts and Flagger.
