Skip to main content
affpapa.org
RU EN
skill GitHub Copilot official · GitHub

gem-devops-guidelines — GitHub Copilot skill: guide & setup

A set of rules for infrastructure reviews, CI/CD pipelines, Docker, Kubernetes, and rollbacks. Guides production readiness and mobile releases in GitHub Copilot.

Install into GitHub Copilot · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add github/awesome-copilot --skill gem-devops-guidelines
Open on GitHub

What gem-devops-guidelines does

This skill sets guardrails for infrastructure design and deployment reviews. It requires pinning base container tags such as node:22-alpine instead of :latest, configuring multi-stage Docker builds under a non-root user, and validating environment variables on startup. Pull request pipelines are split into linting, type checks, unit tests, and preview steps.

The guide outlines rolling, blue-green, and canary deployments. Feature flags must have an owner, an expiration trigger, and code removal within two weeks of reaching 100%. A dedicated section defines mobile releases via Fastlane and EAS, keeping signing credentials outside Git repositories.

Install this if you use Copilot to draft deployment manifests. It prevents default traps like unpinned base images or missing SIGTERM handlers.

What it helps with

  • audit Dockerfiles for multi-stage builds and pinned base images
  • configure Kubernetes readiness and liveness probes
  • define PR and main CI/CD deployment pipelines
  • manage feature flag lifecycles with mandatory rollback triggers
  • standardize mobile deployment workflows using Fastlane or EAS

Example prompts for the agent

  • Review this Dockerfile against the gem-devops-guidelines
  • Generate a production readiness checklist for our backend service
  • Create a rollback plan for a Kubernetes rollout

How to install gem-devops-guidelines

1Skills CLI (Vercel)

npx skills add github/awesome-copilot --skill gem-devops-guidelines

2GitHub CLI

gh skill install github/awesome-copilot gem-devops-guidelines

3Manually: put the files in place

.github/skills/gem-devops-guidelines/SKILL.md

From the same set554

The whole set →
git-commit official github This skill reviews Git changes, stages related files, and creates Conventional Commits. Use it when you want an agent to make one commit or split work into separate commits. GitHub Copilot 47,165installs excalidraw-diagram-generator official github Turn a plain-language description into an Excalidraw diagram. Useful for mapping processes, system structure, and relationships between entities. GitHub Copilot 31,639installs multi-stage-dockerfile official github This skill guides GitHub Copilot in writing multi-stage Dockerfiles for different languages and frameworks. Use it when the final runtime image should contain fewer build dependencies. GitHub Copilot 29,688installs documentation-writer official github Skill that turns the agent into a technical writer following the Diátaxis framework: tutorials, how-to guides, reference, and explanation. Proposes structure before writing. GitHub Copilot 27,757installs prd official github Turns a feature idea into a structured PRD with user stories, technical requirements, and risks. Use it when planning a software feature or an AI-powered one. GitHub Copilot 24,035installs refactor official github This skill reshapes existing code without changing its external behavior. Use it for gradual cleanup of large functions, duplication, weak types, and code smells. GitHub Copilot 22,321installs java-springboot official github Gives GitHub Copilot Spring Boot development practices, from project layout to tests and security. Use it when writing or reviewing Java application code. GitHub Copilot 21,272installs create-readme official github This skill reviews a project and creates a structured README.md. Use it when the repository needs clear documentation based on its actual files and code. GitHub Copilot 19,081installs

Similar

wizard Matt Pocock This skill creates an interactive bash wizard for manual setup steps, CI secrets, third-party dashboards, and one-off migrations. Claude Code 553,369installs hyperframes-cli heygen-com Controls HyperFrames video workflows from the CLI: audits layouts and contrast, edits timeline clips, captures snapshots, and renders locally or in cloud runtimes. Claude Code CX Codex Cursor +1 1,200,000installs setup-pre-commit Matt Pocock This skill configures pre-commit checks for a JavaScript repository, running Prettier, type checking, and tests before each commit. Claude Code 489,289installs using-git-worktrees Jesse Vincent Prepares an isolated workspace before feature work or plan execution. It checks the repository first, then uses native worktree support or Git. Claude Code CX Codex 217,153installs finishing-a-development-branch Jesse Vincent This skill checks the test suite and guides branch completion: merge locally, open a Pull Request, or leave the work in place. Claude Code CX Codex 214,439installs orca-cli stablyai The skill lets an agent manage Orca worktrees, terminals, artifacts and the built-in browser through the orca CLI. Useful when your work already runs inside Orca. Claude Code CX Codex Cursor +1 353,000installs

Questions about gem-devops-guidelines

How do I install gem-devops-guidelines in GitHub Copilot?

Run gh skill install github/awesome-copilot gem-devops-guidelines or place the file at .github/skills/gem-devops-guidelines/SKILL.md.

What does gem-devops-guidelines do?

It injects structured guidelines for Docker, Kubernetes, CI/CD pipelines, health checks, and production readiness into your Copilot environment.

How does the skill handle feature flags?

Each flag requires an owner, an expiration, and a rollback trigger, with dead code and flags removed within two weeks after reaching 100% rollout.

Source text

SKILL.md · MIT 
---
name: gem-devops-guidelines
description: Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mobile release workflows. Use for DevOps, platform, container, pipeline, or release tasks.
---

# DevOps Guidelines

Apply only sections relevant to workload/provider/environment/acceptance criteria. Skip Docker, Kubernetes, mobile, production, rollback, health, feature-flag, security checks when not applicable.

## Deployment strategy

- Rolling (default): gradual, zero-downtime replacement.
- Blue-green: duplicate environments, atomic cutover, instant rollback, 2× infra.
- Canary: route small % first; requires traffic splitting.

## Docker

- Pin base-image tags (`node:22-alpine`); NEVER `:latest`.
- Multi-stage builds + non-root user. Copy deps first for caching.
- `.dockerignore`: `node_modules`, `.git`, tests. Define `HEALTHCHECK` + resource limits.

## Kubernetes

Configure startup, readiness, liveness probes with workload-appropriate initial delays/thresholds.

## CI/CD

- PR: lint -> typecheck -> unit -> integration -> preview.
- Main: build -> staging -> smoke -> production.

## Health and shutdown

- Simple: `GET /health` -> `{ "status": "ok" }`.
- Detailed: dependencies, uptime, version.
- Services MUST expose meaningful health + gracefully handle `SIGTERM` when workload requires it.

## Configuration

Use environment variables (Twelve-Factor), separated by environment. Validate at startup + fail fast. NEVER commit secrets or hard-code `NODE_ENV=production`.

## Rollback

- Kubernetes: `kubectl rollout undo`.
- Vercel: `vercel rollback`.
- Docker: redeploy previous pinned image.

## Feature Flags

- Lifecycle: create -> enable -> 5% -> 25% -> 50% -> 100% -> remove flag + dead code.
- Every flag MUST have owner, expiration, rollback trigger. Remove within two weeks.

## Checklists

- Pre-deploy: passing tests, code review, env vars, migrations, rollback plan.
- Post-deploy: healthy, monitored, old pods terminated, outcome documented.
- Production: passing tests; no hardcoded secrets; JSON logs; meaningful health; pinned versions; validated env vars; resource limits; TLS; CVE scan; CORS; rate limiting; CSP/HSTS/X-Frame-Options; tested rollback; runbook; on-call.
- Apply security/CVE checks to executable or security-sensitive workloads.

## Mobile Deployment

- EAS: `eas build:configure`; `eas build -p ios|android --profile preview`; `eas update --branch production`; `--auto-submit`.
- Fastlane: iOS `match`/`cert`/`sigh`/`pilot`; Android Gradle/`supply`.
- Credentials in env/secret storage, never Git. Automate iOS signing with `fastlane match`; use `keytool` + Google Play App Signing for Android.
- TestFlight: internal instant; external 90 days/100 testers. Google Play: internal/beta/production. Expect 1–7 days review.
- Rollback: EAS `eas update:rollback`; native release -> revert build; store release -> reduce phased rollout.

© github · MIT · github/awesome-copilot

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor