devops-engineer

Automate Kubernetes, Helm, Pulumi, and CI/CD workflows with read-before-change gates.

15|3|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/LazyIsEfficient/agentic-os --skill devops-engineer-lazyisefficient
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devops-engineer
Source: https://github.com/LazyIsEfficient/agentic-os/tree/main/.claude/skills/devops-engineer
Command: npx skills add https://github.com/LazyIsEfficient/agentic-os --skill devops-engineer-lazyisefficient

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Infrastructure and platform teams struggle to consistently manage Kubernetes day-2 operations, IaC tooling, and CI/CD pipelines across environments. This skill codifies guardrails, repeatable workflows, and explicit change-management practices to reduce drift and outages.

Core Features & Use Cases

  • Read-before-change discipline for kubectl, Helm, Pulumi, and CI/CD tooling to prevent unsafe mutations.
  • End-to-end management of Kubernetes resources, Helm charts, and Pulumi stacks across cloud and on-prem environments.
  • CI/CD governance for environment promotion, artifact handling, RBAC design, and secure secret management.

Quick Start

Create a new deployment using Pulumi and Helm in a GitOps workflow and run a diff before applying.

Frequently Asked Questions about devops-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a read-before-change discipline for Kubernetes and Pulumi workflows?

To enforce read-before-change discipline for Kubernetes and Pulumi, you must inspect current resource states using kubectl or pulumi preview before applying mutations. This practice prevents unsafe modifications and reduces infrastructure drift across environments.

What is the best way to automate Helm chart deployments with dry-run gates?

The best way to automate Helm chart deployments with dry-run gates is to integrate helm diff into your CI/CD pipeline. This validates chart changes against the live cluster state, ensuring version-pinned deployments proceed only after verifying the explicit diff.

Can I manage Kubernetes RBAC and secrets across both cloud and on-prem environments?

Yes, you can manage Kubernetes RBAC and secrets across cloud and on-prem environments. The workflow supports secure RBAC design and secrets management practices uniformly, ensuring consistent access controls and governance regardless of the underlying infrastructure.

How do I integrate Pulumi preview and up commands into a CI/CD pipeline?

To integrate Pulumi preview and up commands into a CI/CD pipeline, you configure environment promotion stages that execute pulumi preview as a dry-run gate. Successful validation then triggers pulumi up to apply infrastructure-as-code changes securely.

Does this approach support infrastructure-as-code governance for day-2 Kubernetes operations?

Yes, this approach supports infrastructure-as-code governance for day-2 Kubernetes operations. It codifies guardrails and repeatable workflows for cluster administration, artifact handling, and environment promotion to reduce outages and configuration drift.