devops

Generates Docker, CI/CD pipelines, Terraform infrastructure, and monitoring configurations for deployments.

1|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/sundarshahi/drydock --skill devops-sundarshahi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devops
Source: https://github.com/sundarshahi/drydock/tree/main/skills/devops
Command: npx skills add https://github.com/sundarshahi/drydock --skill devops-sundarshahi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up deployment infrastructure by hand means writing Dockerfiles, CI/CD workflows, Terraform modules, and monitoring configs from scratch, which is slow and error-prone. This Skill generates the full DevOps stack with blocking quality gates wired in. ## Core Features & Use Cases - CI/CD Pipeline Generation: Fills in lint-clean GitHub Actions templates (ci.yml, pr-checks.yml, cd-staging.yml, cd-production.yml) with coverage gates, SAST, Trivy scanning, SLSA provenance, and cosign signing. - Infrastructure as Code: Produces Terraform module structures for AWS, GCP, and Azure covering networking, compute, database, messaging, storage, and security. - Container Orchestration: Creates multi-stage Dockerfiles, Kubernetes base/overlay manifests, and Argo Rollouts canary deployments with automatic rollback. - Use Case: Describe a new service deployment and receive a complete infrastructure setup — Dockerfiles, GitHub Actions workflows with OIDC keyless auth, Terraform environments, Prometheus/Grafana monitoring, and a canary rollout that auto-aborts on error-rate or latency breaches. ## Quick Start Ask the drydock orchestrator to set up deployment infrastructure for your project, or invoke the devops skill directly to generate CI/CD pipelines and Terraform modules.

Frequently Asked Questions about devops

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?▼

Copy the provided templates (ci.yml, pr-checks.yml, cd-staging.yml, cd-production.yml) into .github/workflows/ and replace every placeholder token. The templates include lint, test, coverage gates, SAST, Trivy scanning, and OIDC-based cloud authentication, and must pass actionlint before merging.

How to deploy containers with canary releases on Kubernetes?▼

Use the Argo Rollouts template, which shifts traffic in steps of 10%, 25%, 50%, and 100% while running Prometheus analysis on error burn rate and p99 latency. A failed analysis automatically aborts the rollout and rolls back to the prior immutable image digest.

Does this support cloud providers other than AWS?▼

Yes, the Terraform phase covers AWS, GCP, and Azure with equivalent resource mappings, such as ECS/EKS, Cloud Run/GKE, and Container Apps/AKS for compute. Provider blocks and modules are generated for each target cloud.

Why should CI pipelines avoid long-lived cloud credentials?▼

Long-lived secrets like AWS access keys stored in CI are a supply-chain risk if leaked. The generated workflows use keyless OIDC with id-token permissions to assume a cloud role, with the trust relationship defined as a checked-in Terraform module.

What happens when a coverage or performance gate fails?▼

The production-ready status is blocked because gates exit non-zero with no continue-on-error allowed. A breach can only be cleared through a logged override entry recording the gate, justification, approver, and date.