| name | cc-devops-skills |
| description | SRE, DevOps, Kubernetes, CI/CD, PromQL, Terraform, Docker, and incident operations playbook for building reliable delivery and operations workflows. |
| zh_description | 用于cc、DevOps、技能，支持部署、监控、排障和发布管理。 |
| version | 1.0.0 |
| author | seaworld008 |
| source | github:akin-ozer/cc-devops-skills |
| source_url | https://github.com/akin-ozer/cc-devops-skills |
| license | Apache-2.0 |
| tags | [sre, devops, kubernetes, cicd, promql, terraform, docker, observability, incident-response] |
| created_at | 2026-06-03 |
| updated_at | 2026-06-03 |
| quality | 4 |
| complexity | advanced |
CC DevOps Skills
Use this skill when working on infrastructure, delivery pipelines, Kubernetes operations, observability, PromQL, incident response, Terraform, Docker, shell automation, and reliability engineering. It provides a unified SRE/DevOps operating model rather than a single vendor-specific command set.
The skill is inspired by the Apache-2.0 cc-devops-skills repository, but this version is self-contained for this curated skill catalog.
When to Use
- Designing, reviewing, or fixing CI/CD pipelines.
- Creating or validating Kubernetes manifests, Helm values, Kustomize overlays, or deployment workflows.
- Debugging pods, services, ingress, DNS, network policy, probes, autoscaling, or rollout issues.
- Writing PromQL queries, alert rules, recording rules, SLO dashboards, or runbooks.
- Building Dockerfiles, Compose stacks, image hardening, or multi-stage builds.
- Reviewing Terraform, Terragrunt, Ansible, or infrastructure-as-code changes.
- Handling incidents, postmortems, operational readiness, release safety, and rollback planning.
- Improving reliability, deployment frequency, recovery time, observability, and operational toil.
Skip When
- The task is pure application logic without deployment, runtime, reliability, or operational impact.
- The user asks for business strategy, product design, or frontend-only polish.
- A cloud-provider-specific skill already covers the whole task more precisely, such as a deep Azure Kubernetes operation.
Core Capabilities
- Translate product and engineering needs into reliable delivery systems.
- Build CI/CD workflows with clear stages, caching, artifact flow, gates, and rollback paths.
- Design Kubernetes resources with probes, requests, limits, disruption budgets, security context, and deployment strategy.
- Debug live clusters using repeatable evidence gathering.
- Write PromQL that respects labels, cardinality, windows, and alert semantics.
- Review infrastructure-as-code for drift, blast radius, secrets, and lifecycle risk.
- Harden containers and supply-chain paths.
- Produce incident runbooks and postmortem-ready timelines.
Operating Principles
- Automate the path, but make the failure mode visible.
- Prefer declarative infrastructure and reproducible builds.
- Treat secrets as toxic data: never print, commit, or echo them.
- Every alert needs an owner, severity, symptom, impact, and action.
- Every deployment needs a rollback or forward-fix decision point.
- Production changes should be observable before they are trusted.
