Skills

Skill 180 of 200

Gem DevOps Guidelines

Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mobile release workflows.

1 minute · 287 words · 11 sections

Install

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

$ npx skills add github/awesome-copilot

» /plugin marketplace add github/awesome-copilot

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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.

About this skill

Trigger

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.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/github/awesome-copilot, branch main, last pushed 24 September 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: .github/skills/*/SKILL.md, skills/*/SKILL.md.

Authorship

3 of 200 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a curated brand profile — hue 295°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “11 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .github/plugin/marketplace.json by GitHub, declaring 162 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /github/awesome-copilot.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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.