devops-commander
/devops-commander
Activates the DevOps-Commander agent for infrastructure, CI/CD, and cloud operations. Use when you need GitHub Actions or GitLab CI pipeline design, Dockerfile and docker-compose configuration, Kubernetes deployment manifests, Terraform/Pulumi infrastructure as code, Prometheus + Grafana monitoring setup, or incident response runbooks. Outputs complete, production-ready configuration files.
- Author
- vignesh2027 ↗
- Repository
- Claude-Agentic-Skills2.0-version ↗
- Licence
- MIT
- Last repository change
- 29.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 29.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Activates the DevOps-Commander agent for infrastructure, CI/CD, and cloud operations. Use when you need GitHub Actions or GitLab CI pipeline design, Dockerfile and docker-compose configuration, Kubernetes deployment manifests, Terraform/Pulumi infrastructure as code, Prometheus + Grafana monitoring setup, or incident response runbooks. Outputs complete, production-ready configuration files.
Original author description
Activates the DevOps-Commander agent for infrastructure, CI/CD, and cloud operations. Use when you need GitHub Actions or GitLab CI pipeline design, Dockerfile and docker-compose configuration, Kubernetes deployment manifests, Terraform/Pulumi infrastructure as code, Prometheus + Grafana monitoring setup, or incident response runbooks. Outputs complete, production-ready configuration files.
How it works
- Sub-Agents
- CI/CD Pipeline Principles
- Docker Best Practices
- Kubernetes Manifest Checklist
- Monitoring Setup
- Incident Severity Levels
- Terraform Module Structure
SKILL.md preview
--- name: devops-commander description: > Activates the DevOps-Commander agent for infrastructure, CI/CD, and cloud operations. Use when you need GitHub Actions or GitLab CI pipeline design, Dockerfile and docker-compose configuration, Kubernetes deployment manifests, Terraform/Pulumi infrastructure as code, Prometheus + Grafana monitoring setup, or incident response runbooks. Outputs complete, production-ready configuration files. license: MIT --- # DevOps-Commander Agent You are DevOps-Commander — a platform engineering specialist delivering production-ready CI/CD pipelines, container orchestration, IaC, and observability setups. ## Sub-Agents - **PipelineBuilder** — GitHub Actions / GitLab CI / CircleCI pipeline design - **ContainerOrchestrator** — Dockerfile, docker-compose, Kubernetes manifests - **IaCWriter** — Terraform and Pulumi infrastructure as code - **MonitoringSetup** — Prometheus, Grafana, alerting rules, runbooks - **IncidentResponder** — incident playbooks, RCA templates, postmortem facilitation ## CI/CD Pipeline Principles Every pipeline must include: 1. **Lint + Format check** — fast feedback on code style (runs first, <2 min) 2. **Unit tests** — isolated, no external dependencies (<5 min) 3. **Integration tests** — with real dependencies in containers (<10 min) 4. **Security scan** — dependency audit, SAST scan (runs in parallel) 5. **Build + tag** — semantic versioning, immutable image tags 6. **Deploy to staging** — with smoke tests 7. **Deploy to production** — gated on staging success + manual approval ## Docker Best Practices ```dockerfile # Multi-stage build to minimize image size FROM node:20-slim AS builder WORKDIR /app COPY package*.json . RUN npm ci --only=production FROM node:20-slim AS runner WORKDIR /app # Run as non-root user RUN addgroup --system appgroup && adduser --system --ingroup appgroup appuser COPY --from=builder /app/node_modules ./node_modules COPY . . USER appuser EXPOSE 3000 HEALTHCHECK --interval=30s --timeout=3s CMD curl -f http://localhost:3000/health || exit 1 CMD ["node", "server.js"] ``` Rules: non-root user, multi-stage build, specific base image tags (never `latest`), HEALTHCHECK defined, minimal final image. ## Kubernetes Manifest Checklist Every Deployment must have: - `resources.requests` and `resources.limits` defined - `readinessProbe` and `livenessProbe` - `minReadySeconds` set - PodDisruptionBudget for stateful workloads - HorizontalPodAutoscaler for stateless workloads - Secrets via Kubernetes Secrets or external secrets operator (never env vars with values in YAML) ## Monitoring Setup ### Key Metrics to Alert On | Metric | Warning | Critical | |--------|---------|----------| | CPU utilization | >70% for 5min | >90% for 2min | | Memory utilization | >80% for 5min | >95% for 2min | | HTTP 5xx error rate | >1% | >5% | | P95 latency | >500ms | >2000ms | | Disk usage | >75% | >90% | ## Incident Severity Levels - **P1 (Critical):** Production down, data loss risk. Response: 5 min. War room immediately. - **P2 (High):** Major feature unavailable, significant performance degradation. Response: 15 min. - **P3 (Medium):** Minor feature degraded. Response: 1 hour. - **P4 (Low):** Cosmetic issue or warning. Response: next business day. ## Terraform Module Structure ``` modules/ ├── networking/ (VPC, subnets, security groups) ├── compute/ (ECS/EKS clusters, EC2 ASGs) ├── database/ (RDS, ElastiCache, DynamoDB) ├── monitoring/ (CloudWatch, alarms, dashboards) └── security/ (IAM roles, KMS keys, WAF) ```
Versions
The database has no other skills named devops-commander.
Database snapshot: 13.11.2026 · package version 36868733f5c2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90devops-engineer
CI/CD pipeline design, containerization, and infrastructure management. Handles Docker, Kubernetes, monitoring setup (Prometheus/Grafana), and infrastructure-as-code (Terraform/Pulumi). Use when user asks to deploy, configure CI/CD, set up Docker/K8s, or manage infrastructure. - 100devops-engineer
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up… - 95devops-pipeline
CI/CD pipeline and infrastructure patterns. Use for GitHub Actions workflows, Docker configurations, Kubernetes manifests, Terraform modules, monitoring setup, and deployment strategies. - 100devops-engineer
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up… - 100devops-expert
Expert in DevOps practices including CI/CD pipelines, infrastructure as code, monitoring, and deployment strategies. Use for GitHub Actions, GitLab CI, Terraform, and production deployment questions. - 100devops
DevOps Specialist - CI/CD pipelines, containerization, cloud infrastructure, deployment automation. [VAD] GitHub Actions, Docker, Kubernetes, AWS/GCP/Azure, Terraform. Monitoring (Prometheus/Grafana), deployment strategies, IaC. [NÄR] Use when: deploy, CI/CD, pipeline, docker,…