devops-engineer

Generates Dockerfiles, CI/CD pipelines, Kubernetes manifests, and Terraform infrastructure configurations.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/Yash-Awasthi/adapfit --skill devops-engineer-yash-awasthi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devops-engineer
Source: https://github.com/Yash-Awasthi/adapfit/tree/main/.agents/skills/devops-engineer
Command: npx skills add https://github.com/Yash-Awasthi/adapfit --skill devops-engineer-yash-awasthi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up deployment infrastructure requires deep knowledge of Docker, Kubernetes, Terraform, and CI/CD systems, and mistakes in these configurations cause outages, security gaps, and slow releases. This Skill produces production-oriented infrastructure code and operational runbooks with built-in safety practices like approval gates, rollback procedures, and secret management. ## Core Features & Use Cases - CI/CD Pipeline Generation: Creates GitHub Actions and GitLab CI pipelines with testing, image building, security scanning, and staged deployments. - Container & Orchestration Configs: Writes multi-stage Dockerfiles, Kubernetes deployments with health probes and autoscaling, and GitOps setups with ArgoCD. - Infrastructure as Code: Produces Terraform configurations for AWS resources like ECS Fargate and RDS with state management best practices. - Incident Response: Provides runbook templates, postmortem formats, severity classifications, and rollback procedures for production incidents. - Use Case: You need to containerize a FastAPI app and deploy it to Kubernetes with a GitHub Actions pipeline. The Skill generates the Dockerfile, CI workflow with Trivy scanning, K8s manifests with liveness probes, and a documented rollback procedure. ## Quick Start Ask the assistant to create a CI/CD pipeline and Dockerfile for your application, specifying your tech stack and target platform such as GitHub Actions with Kubernetes.

Frequently Asked Questions about devops-engineer

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

FAQPage Schema
How do I set up a CI/CD pipeline with GitHub Actions?▼

Define a workflow YAML with test, build, and deploy jobs that run on push to main. Use docker/build-push-action to build and push images to a registry, then update Kubernetes deployments with kubectl set image for staging and production environments.

How do I write a Dockerfile for a Python application?▼

Use a multi-stage build: install dependencies in a builder stage, then copy only the installed packages into a slim runtime image. Run as a non-root user, pin the base image version, and add a HEALTHCHECK instruction for container orchestration.

What deployment strategy should I use for Kubernetes?▼

Rolling updates work for standard releases with automatic rollback via health checks. Use blue-green for instant rollback needs, canary with Flagger for gradual risk-managed rollouts, and recreate only for stateful apps with breaking changes.

Can I use GitLab CI instead of GitHub Actions for deployments?▼

Yes, GitLab CI supports the same workflow using .gitlab-ci.yml with stages, needs-based DAG dependencies, and environment declarations. Use workflow rules to prevent duplicate pipelines and OIDC tokens instead of static cloud credentials.

Why should secrets not be stored in CI/CD variables?▼

CI/CD variables can leak through logs, forked merge requests, or misconfigured access controls. Use secret managers like AWS SSM, HashiCorp Vault, or OIDC-based short-lived cloud credentials instead of long-lived static keys.

What are the limitations of automated deployment pipelines?▼

Pipelines still require explicit human approval before production deployments and cannot replace staging environment testing. Rollback procedures must be documented and verified beforehand, and automated remediation should escalate to on-call engineers when it fails.