devops
Provides comprehensive DevOps guidance including CI/CD pipeline design, infrastructure as code (Terraform, CloudFormation, Bicep), container orchestration (Docker, Kubernetes), deployment strategies (blue-green, canary, rolling), monitoring and observability, configuration management (Ansible, Chef, Puppet), and cloud platform automation (AWS, GCP, Azure). Produces deployment scripts, pipeline configurations, infrastructure code, and operational procedures. Use when designing CI/CD pipelines, automating infrastructure, containerizing applications, setting up monitoring, implementing deployment strategies, managing configurations, or when users mention DevOps, CI/CD, infrastructure automation, Kubernetes, Docker, Terraform, deployment, monitoring, or cloud operations.
Works with
--- name: devops description: Provides comprehensive DevOps guidance including CI/CD pipeline design, infrastructure as code (Terraform, CloudFormation, Bicep), container orchestration (Docker, Kubernetes), deployment strategies (blue-green, canary, rolling), monitoring and observability, configuration management (Ansible, Chef, Puppet), and cloud platform automation (AWS, GCP, Azure). Produces deployment scripts, pipeline configurations, infrastructure code, and operational procedures. Use when designing CI/CD pipelines, automating infrastructure, containerizing applications, setting up monitoring, implementing deployment strategies, managing configurations, or when users mention DevOps, CI/CD, infrastructure automation, Kubernetes, Docker, Terraform, deployment, monitoring, or cloud operations. license: MIT --- # DevOps ## Core Capabilities Provides expert guidance covering the entire software delivery lifecycle: 1. **CI/CD Pipeline Design** - Automated build, test, and deployment workflows 2. **Infrastructure as Code** - Cloud resource provisioning with Terraform, CloudFormation, Bicep 3. **Container Orchestration** - Docker and Kubernetes deployment patterns 4. **Deployment Strategies** - Blue-green, canary, and rolling deployments 5. **Monitoring & Observability** - Metrics, logging, alerting with Prometheus, Grafana, ELK 6. **Configuration Management** - Ansible, Chef, Puppet automation 7. **Security & Compliance** - DevSecOps practices and container security ## Best Practices ## CI/CD - Keep pipelines fast (< 10 minutes for feedback) - Fail fast with quick tests first - Use pipeline as code (version controlled) - Implement proper secret management - Enable artifact caching and parallelize independent jobs ### Infrastructure as Code - Use remote state with locking - Create reusable modules and pin versions - Always review plan before apply - Implement proper tagging strategy - Document resource dependencies ### Container Orchestration - Set resource requests and limits - Implement health checks (liveness/readiness probes) - Use pod anti-affinity for high availability - Enable horizontal pod autoscaling - Implement proper logging and monitoring ### Deployment - Use rolling updates with zero downtime - Implement proper health checks and rollback capabilities - Use canary/blue-green for critical applications - Test thoroughly in staging environments - Monitor post-deployment metrics ### Security - Run containers as non-root with read-only root filesystems - Scan images for vulnerabilities regularly - Implement network policies and secrets management - Enable pod security standards and least privilege access ### Monitoring - Collect metrics using RED/USE methods - Implement structured logging with meaningful alerts - Create actionable dashboards and monitor SLIs/SLOs - Set up distributed tracing for microservices ## Detailed References Load reference files based on specific needs: - **CI/CD Pipeline Design**: See [cicd-pipeline-design.md](references/cicd-pipeline-design.md) for: - GitHub Actions, GitLab CI, Jenkins pipeline examples - Automated build, test, deploy workflow patterns - Pipeline optimization and caching strategies - **Infrastructure as Code**: See [infrastructure-as-code.md](references/infrastructure-as-code.md) for: - Terraform, CloudFormation, Bicep patterns - AWS, GCP, Azure resource provisioning - Module design and state management - **Container Orchestration**: See [container-orchestration.md](references/container-orchestration.md) for: - Kubernetes manifests, Helm charts, Kustomize - Docker best practices and multi-stage builds - Service mesh and networking patterns - **Deployment Strategies**: See [deployment-strategies.md](references/deployment-strategies.md) for: - Blue-green deployment implementation - Canary release patterns with traffic splitting - Rolling update strategies and rollback procedures - **Monitoring & Observability**: See [monitoring-and-observability.md](references/monitoring-and-observability.md) for: - Prometheus, Grafana setup and configuration - ELK stack deployment and log aggregation - Alert rules, dashboards, and SLO definitions - **Security Best Practices**: See [security-best-practices.md](references/security-best-practices.md) for: - DevSecOps pipeline integration - Container security scanning and hardening - Secret management and compliance validation - **Configuration Management**: See [configuration-management.md](references/configuration-management.md) for: - Ansible playbooks, Chef recipes, Puppet manifests - Server configuration automation patterns - Infrastructure drift detection - **Common Commands**: See [common-commands.md](references/common-commands.md) for: - Kubernetes kubectl command reference - Docker CLI operations - Terraform and cloud provider CLI commands - **Troubleshooting**: See [troubleshooting-guide.md](references/troubleshooting-guide.md) for: - Common issues and resolution steps - Debugging techniques for containers and orchestration - Performance optimization strategies
More Deployment & CI/CD skills
azure-enterprise-infra-planner
microsoft/azure-skills
Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows.
azure-kubernetes-app-deploy
microsoft/azure-skills
Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster, containerize app for Kubernetes, generate K8s manifests for Azure, set up CI/CD for AKS, my AKS deployment is failing safeguard checks, I have a Django/Express/Spring Boot app to run on AKS. DO NOT USE FOR: creating or provisioning an AKS cluster (use azure-kubernetes), assessing migration to AKS Automatic (use azure-kubernetes-automatic-readiness), or deploying to non-AKS targets like Web Apps, Container Apps, or Functions.
finetuning
microsoft/azure-skills
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).

