afrexai-devops-engine_skill

This skill helps you design and govern complete DevOps and platform engineering workflows across clouds, IaC, CI/CD, and observability.
  • Python

1.5k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill afrexai-devops-engine

  • _meta.json286 B
  • README.md3.5 KB
  • SKILL.md31.5 KB

Overview

This skill is a complete DevOps and Platform Engineering engine for teams building, deploying, and operating production software across any cloud. It bundles opinionated patterns for branching, CI/CD pipelines, container strategy, infrastructure-as-code, and Kubernetes operations. The goal is reproducible, observable, and secure delivery pipelines that scale with team size and compliance requirements.

How this skill works

The engine inspects repository layout and applies a recommended branch and commit strategy, then generates a reusable CI/CD pipeline template that enforces build-once deploy-everywhere and fail-fast principles. It provides Dockerfile patterns, caching strategies, and security scanning steps for images. For infrastructure it prescribes IaC layouts, remote state safety rules, and an environment promotion workflow; for Kubernetes it supplies production-ready manifests, autoscaling, and Helm chart checklists.

When to use it

  • Setting up a new microservice or monorepo with consistent CI/CD and branch controls
  • Migrating from ad-hoc build scripts to reproducible, hermetic pipelines and immutable artifacts
  • Standardizing container builds, image scanning, and local developer compose setups
  • Implementing multi-environment IaC with remote state and safe promotion gates
  • Hardening Kubernetes deployments: probes, resource limits, autoscaling, and rollout strategies
  • Preparing for audits or regulated releases with signed tags and stricter branch protection

Best practices

  • Adopt a branch strategy matched to team size and release cadence; protect main with mandatory checks and PRs
  • Build once and tag artifacts with the Git SHA; promote the same artifact through dev→staging→prod
  • Fail fast: run lint/typecheck/security in parallel before slower tests; enforce coverage thresholds
  • Use multi-stage Docker builds, minimal base images, and image scanners like Trivy in CI
  • Keep Terraform state remote with locking, always plan before apply, and protect critical resources from destroy
  • Define Kubernetes readiness/liveness probes, requests/limits, PDBs, and run non-root containers

Example use cases

  • Generate a reusable GitHub Actions workflow that builds, scans, and deploys canary releases to production
  • Create a Terraform project structure with remote S3/GSM state and review-in-PR promotion to environments
  • Replace manual docker builds with multi-stage Dockerfiles and integrate Trivy vulnerability gating in CI
  • Ship a Helm chart that includes network policies, external secrets integration, and CI linting/templates in pipeline
  • Operate a Kubernetes service with HPA, rolling updates, topology spread, and controlled rollback windows

FAQ

Yes. The patterns map to GitHub Actions, GitLab CI, CircleCI, and Jenkins; adapt the provided universal template to your CI syntax.

How do I keep builds reproducible?

Use hermetic build environments, pin base images, cache dependencies by lockfile hash, tag artifacts with the commit SHA, and avoid external mutable state during builds.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
afrexai-devops-engine skill by openclaw/skills | VeilStrat