devops

Configure and validate cloud deployments and CI/CD pipelines for containerized web applications.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/gfcampos1/my-skills --skill devops-gfcampos1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devops
Source: https://github.com/gfcampos1/my-skills/tree/main/skills/devops
Command: npx skills add https://github.com/gfcampos1/my-skills --skill devops-gfcampos1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill reduces the complexity of launching and maintaining production-ready deployments by providing a reproducible approach to platform selection, containerization, CI/CD, infrastructure as code, secrets management, and observability. It helps teams avoid common deployment mistakes, insecure secret handling, and missing monitoring that lead to outages or slow recoveries.

Core Features & Use Cases

  • Workspace detection: Automatically detect existing infra signals (Dockerfile, railway.json, fly.toml, .github/workflows, terraform/) and follow established conventions.
  • Platform selection guidance: Recommend the top two platform choices (Railway, Fly.io, Render, Vercel, AWS, GCP) with tradeoffs based on app type, traffic, budget, and compliance needs.
  • Containerization best practices: Produce multi-stage Dockerfiles, .dockerignore recommendations, and runtime non-root user configuration.
  • CI/CD templates: Provide GitHub Actions patterns for typecheck, test, build, and deploy with caching and secrets injected securely.
  • Observability & checklist: Define health endpoints, structured JSON logging, Sentry error tracking, uptime monitoring, metrics, and a pre-deploy checklist for secrets, builds, and security.
  • Use Case: Convert a monorepo Node.js/Vite + Express app into a CI-backed Railway or Fly.io deployment with a multi-stage Dockerfile, automated tests, and Sentry monitoring.

Quick Start

Deploy a Node.js app using a multi-stage Dockerfile and a GitHub Actions pipeline that runs lint, test, build, and deploys to your chosen platform on the main branch.

Frequently Asked Questions about devops

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

FAQPage Schema
How do I configure a multi-stage Dockerfile for a Node.js web application?

A multi-stage Dockerfile for a Node.js application separates the build environment from the production runtime to minimize image size and enhance security. This approach uses distinct build and runtime stages, incorporates a .dockerignore file, and configures a non-root user for secure execution.

What's the best way to set up GitHub Actions CI/CD pipelines with caching and secrets?

Setting up GitHub Actions CI/CD pipelines involves creating workflows for typecheck, test, build, and deploy stages. The pipeline leverages caching for dependencies and securely injects repository or environment secrets during the deployment process to prevent unauthorized access.

How do I choose between Railway, Fly.io, Render, and Vercel for deploying my containerized app?

Choosing between Railway, Fly.io, Render, and Vercel depends on your application type, expected traffic volume, budget constraints, and compliance requirements. The selection process evaluates these tradeoffs to recommend the top two platforms best suited for your specific deployment scenario.

How do I add observability and Sentry error tracking to a Python or Go deployment?

Adding observability to a Python or Go deployment requires defining health endpoints, implementing structured JSON logging, and integrating Sentry for error tracking. This configuration also includes uptime monitoring and metrics collection to quickly identify and recover from production outages.

Can I use basic Terraform infrastructure patterns for CI/CD deployments on AWS or GCP?

Yes, you can use basic Terraform infrastructure patterns to provision resources on AWS or GCP for CI/CD deployments. This infrastructure as code approach provides a reproducible method to manage cloud resources, reducing manual configuration errors and ensuring environment consistency across deployments.