devops
npx machina-cli add skill Fujigo-Software/f5-framework-claude/devops --openclawDevOps Skills
Overview
DevOps practices for continuous integration, delivery, and operations to enable fast, reliable software delivery.
DevOps Lifecycle
┌─────────────────────────────────────────────────────────────────┐
│ CONTINUOUS │
│ ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ ┌───────┐ │
│ │ Plan │→ │ Code │→ │Build │→ │ Test │→ │Release│ │
│ └──────┘ └──────┘ └──────┘ └──────┘ └───────┘ │
│ ↑ │ │
│ │ INTEGRATION / DELIVERY ↓ │
│ ┌──────┐ ┌───────┐ ┌──────┐ │
│ │Learn │← │Monitor│← │Deploy│ │
│ └──────┘ └───────┘ └──────┘ │
│ OPERATIONS │
└─────────────────────────────────────────────────────────────────┘
Categories
CI/CD
- Pipeline fundamentals
- GitHub Actions / GitLab CI
- Pipeline patterns
- Deployment strategies (Blue-Green, Canary)
Containerization
- Docker fundamentals
- Docker Compose
- Container best practices
- Multi-stage builds
Orchestration
- Kubernetes basics
- Helm charts
- Service mesh
- GitOps (ArgoCD, Flux)
Monitoring
- Metrics and SLIs/SLOs
- Prometheus & Grafana
- Alerting strategies
- Dashboard design
Logging
- Structured logging
- Log aggregation
- ELK/EFK stack
- Distributed tracing
Infrastructure
- Infrastructure as Code
- Terraform
- Cloud patterns
- Cost optimization
Reliability
- SRE fundamentals
- Incident management
- Chaos engineering
- Disaster recovery
DORA Metrics
| Metric | Elite | High | Medium | Low |
|---|---|---|---|---|
| Deployment Frequency | On-demand | Weekly | Monthly | Yearly |
| Lead Time | < 1 day | 1 week | 1 month | > 6 months |
| Change Failure Rate | < 15% | 16-30% | 31-45% | > 45% |
| MTTR | < 1 hour | < 1 day | < 1 week | > 1 week |
Skills Index
CI/CD
Containerization
Orchestration
Monitoring
Logging
Infrastructure
Reliability
DevOps Maturity Model
┌─────────────────────────────────────────────────────────────────┐
│ DevOps Maturity Levels │
├─────────────────────────────────────────────────────────────────┤
│ │
│ Level 5: Optimizing │
│ ├── Continuous improvement culture │
│ ├── Predictive analytics │
│ └── Self-healing systems │
│ │
│ Level 4: Measured │
│ ├── Comprehensive metrics │
│ ├── Data-driven decisions │
│ └── Automated compliance │
│ │
│ Level 3: Defined │
│ ├── Standardized pipelines │
│ ├── Infrastructure as Code │
│ └── Centralized logging/monitoring │
│ │
│ Level 2: Managed │
│ ├── Basic CI/CD │
│ ├── Some automation │
│ └── Manual deployments │
│ │
│ Level 1: Initial │
│ ├── Ad-hoc processes │
│ ├── Manual everything │
│ └── Siloed teams │
│ │
└─────────────────────────────────────────────────────────────────┘
Best Practices
- Automate Everything - Reduce manual toil
- Version Control All - Code, configs, infrastructure
- Shift Left - Test and secure early
- Measure What Matters - Focus on DORA metrics
- Embrace Failure - Learn from incidents
- Continuous Improvement - Iterate and optimize
- Collaboration - Break down silos
- Documentation - Runbooks and playbooks
Source
git clone https://github.com/Fujigo-Software/f5-framework-claude/blob/main/plugins/f5-core/skills/devops/SKILL.mdView on GitHub Overview
DevOps skills cover continuous integration, delivery, and operations to enable fast, reliable software delivery. It combines automation, culture, and monitoring to shorten feedback loops from code to production.
How This Skill Works
It relies on automated CI/CD pipelines (e.g., GitHub Actions, GitLab CI) to build, test, and release code. Infrastructure as Code (Terraform) and container orchestration (Kubernetes) provide repeatable environments, while monitoring, logging, and SRE practices ensure reliability.
When to Use It
- When teams need faster, safer software delivery with automated builds and tests
- When migrating apps to containers and orchestration (Docker, Kubernetes)
- When adopting GitOps for declarative deployments
- When improving reliability with SRE basics, incident management, and observability
- When optimizing cloud costs and applying cost-aware infrastructure patterns
Quick Start
- Step 1: Map your tech stack and pick CI/CD and IaC tools (e.g., GitHub Actions + Terraform)
- Step 2: Create a basic pipeline that builds, tests, and promotes code to a staging environment
- Step 3: Add deployment strategies (blue-green/canary) and basic monitoring
Best Practices
- Adopt Infrastructure as Code (IaC) for reproducible environments
- Version-control CI/CD pipelines and IaC configurations
- Use deployment strategies like blue-green or canary to minimize risk
- Define and monitor SLIs/SLOs with alerting and dashboards
- Implement structured logging and distributed tracing for observability
Example Use Cases
- A team implements GitHub Actions CI/CD to build, test, and deploy to Kubernetes
- Terraform-powered infrastructure provisioning aligned with cloud provider patterns
- Canary deployment with feature flags and a service mesh
- Prometheus and Grafana dashboards track SLIs/SLOs and MTTR
- Disaster recovery drills and incident response playbooks in regular use
Frequently Asked Questions
Related Skills
accessibility
Fujigo-Software/f5-framework-claude
Web accessibility guidelines and implementation
api-design
Fujigo-Software/f5-framework-claude
API design principles for REST, GraphQL, and gRPC
database
Fujigo-Software/f5-framework-claude
Database design, SQL, NoSQL, and data management
performance
Fujigo-Software/f5-framework-claude
Performance optimization strategies and techniques
code-quality
Fujigo-Software/f5-framework-claude
Code quality practices, linting, and refactoring
git
Fujigo-Software/f5-framework-claude
Git version control and collaboration workflows
