DevOps

**Judgement:** This skill is a strong, opinionated DevOps best‑practices reference that can significantly improve the quality of CI/CD, infrastructure, and operations decisions, especially when an agent is generating or reviewing DevOps‑related configurations and workflows. **What it’s good for:** - Serving as a checklist or north star for designing CI/CD pipelines, including test ordering, caching, and parallelization. - Guiding infrastructure‑as‑code patterns (Terraform/Ansible/CloudFormation), state handling, and environment separation. - Informing container build and deployment patterns (non‑root, health checks, immutable images, SHA tagging). - Shaping safe deployment strategies (blue‑green, canary, rolling) and emphasizing rollback planning and artifact promotion. - Elevating operational maturity via monitoring/alerting based on golden signals, SLOs/error budgets, chaos engineering, and runbooks. **Key risks / limitations:** - It is a ruleset, not an automation engine: it doesn’t provide concrete, tool‑specific code or workflows by itself. - Some guidance is intentionally high‑level and may need adaptation to organization‑specific constraints, compliance needs, or legacy systems. - It appears vendor‑neutral and generic; users needing very detailed, platform‑specific instructions (e.g., exact GitHub Actions YAML, Kubernetes manifests) will need complementary skills or knowledge. **Recommended scenarios:** Use this skill when you want the agent to: (1) critique or improve CI/CD pipelines and deployment procedures, (2) design or review IaC and container strategies for reliability and security, or (3) enforce consistent DevOps standards across projects. It is less suited as the sole source of truth for detailed, provider‑specific implementation steps.