gem-devops-guidelines

Reviews infrastructure, CI/CD, Docker, Kubernetes, and release workflows against DevOps guidelines.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill gem-devops-guidelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gem-devops-guidelines
Source: https://github.com/github/awesome-copilot/tree/main/skills/gem-devops-guidelines
Command: npx skills add https://github.com/github/awesome-copilot --skill gem-devops-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often ship infrastructure and deployment configurations that miss critical checks like pinned image tags, health probes, rollback plans, or secret management, leading to outages and security gaps. This Skill provides a consolidated checklist of DevOps best practices so reviews and designs stay consistent.

Core Features & Use Cases

  • Deployment & Release Guidance: Covers rolling, blue-green, and canary strategies plus rollback commands for Kubernetes, Vercel, and Docker.
  • Container & Orchestration Rules: Enforces pinned base images, multi-stage builds, non-root users, and Kubernetes startup/readiness/liveness probes.
  • Production Readiness Checklists: Validates health endpoints, graceful shutdown, feature flags, secrets handling, TLS, and security headers before launch.
  • Use Case: Before merging a pull request that adds a new microservice, ask the AI to review the Dockerfile, CI pipeline, and Kubernetes manifests against these guidelines to catch missing health checks or unpinned images.

Quick Start

Review my Dockerfile, CI pipeline, and Kubernetes deployment manifests against the DevOps guidelines and list any violations.

Frequently Asked Questions about gem-devops-guidelines

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

FAQPage Schema
How do I review a Dockerfile against DevOps best practices?

Check that base images use pinned tags like node:22-alpine instead of :latest, builds use multi-stage stages with a non-root user, and dependencies are copied first for caching. Also verify a .dockerignore excludes node_modules and .git, plus a HEALTHCHECK and resource limits are defined.

What should a CI/CD pipeline include for pull requests and main branches?

Pull request pipelines should run lint, typecheck, unit tests, integration tests, and a preview deployment in that order. Main branch pipelines should build, deploy to staging, run smoke tests, then promote to production.

Which deployment strategy should I use: rolling, blue-green, or canary?

Rolling is the default for gradual zero-downtime replacement. Blue-green duplicates environments for atomic cutover and instant rollback at double infrastructure cost, while canary routes a small traffic percentage first and requires traffic splitting support.

How do I roll back a failed Kubernetes or Vercel deployment?

For Kubernetes, run kubectl rollout undo to return to the previous revision. On Vercel use vercel rollback, and for Docker-based deployments redeploy the previous pinned image tag.

What health checks should a production service expose?

A simple service should expose GET /health returning a status payload, while detailed checks report dependencies, uptime, and version. Services must also handle SIGTERM gracefully and configure Kubernetes startup, readiness, and liveness probes with appropriate delays.

When should feature flags be removed from code?

Feature flags follow a lifecycle from creation through gradual rollout at 5%, 25%, 50%, and 100%, then removal of the flag and dead code. Every flag needs an owner, expiration, and rollback trigger, and should be removed within two weeks.