devops-platform
面向可观测、可回滚的生产部署实践，适合运维与平台工程师。
可能会建议高权限操作或变更生产配置，需谨慎评估。
提供生产级容器化、K8s、CI/CD、IaC 与监控告警等平台工程指导。
帮你把应用安全可靠地上线：包含 Docker、Kubernetes、CI/CD、Terraform、GitOps、滚动/蓝绿/金丝雀部署与监控告警（Prometheus/Grafana/Datadog、OpenTelemetry）等实战建议。用在要容器化、写 Dockerfile/manifest、搭流水线或排查 pod crash-loop 时。强调可观测性、回滚与工程化以应付真实故障场景。
▸ 展开 SKILL.md 英文原文
Production-grade DevOps and platform engineering guidance — Docker, Kubernetes, CI/CD pipelines, Terraform/IaC, GitOps, deployment strategies (rolling/blue-green/canary), monitoring and alerting, and cloud patterns across AWS/Azure/GCP. Use this whenever the user asks about containerizing an app, writing a Dockerfile or Kubernetes manifest, setting up CI/CD (GitHub Actions, GitLab CI, Jenkins, Azure DevOps), Terraform/Pulumi infrastructure, ArgoCD/Flux/GitOps, autoscaling, secrets management, observability (Prometheus, Grafana, Datadog, OpenTelemetry), or rollback/deployment strategy — even if they just say "help me deploy this" or "why is my pod crash-looping."
帮我安装这个 skill：https://raw.githubusercontent.com/CODE-SAURABH/OpenSkills/main/devops-platform/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/CODE-SAURABH/OpenSkills/main/devops-platform/SKILL.md"# DevOps & Platform Engineering Approach every platform task as the engineer who gets paged at 3am when it breaks. The pipeline isn't done when it works on the happy path — it's done when a failure is easy to detect, easy to explain, and easy to reverse. Every config decision here exists to serve one of those three properties. --- ## Step 0: Ground the Platform Work Before writing any pipeline, container, or deployment config, get clear on: 1. **What is being deployed?** Stateless service, stateful service, batch job, scheduled task — each has a different deployment shape. 2. **What are the environments?** Dev, staging, prod — what's the promotion path between them, and what gates it? 3