gem-devops-guidelines
Helps your agent plan and review infrastructure and how software is delivered. Useful for setting up continuous delivery systems and ensuring everything works well.
What it does
This tool helps plan and review how a computer program is launched and updated. It covers everything from how to build the program to ensuring it runs well and can be rolled back if issues arise.
When to use it
- ✓When planning how a new program will be released.
- ✓When deciding how to update an existing program without service interruption.
- ✓When setting up the automatic testing and deployment process.
Example of what to ask your AI
“How can I perform a safe release of a new application using the 'canary' strategy?”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool analyzes deployment steps, such as gradually replacing old versions with new ones (rolling) or duplicating environments (blue-green). It also checks important configurations like health checks and how to revert to a previous version if something goes wrong.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add github/awesome-copilot --skill gem-devops-guidelinesOr download just the file:
curl -L https://raw.githubusercontent.com/github/awesome-copilot/main/skills/gem-devops-guidelines/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
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. DefineHEALTHCHECK+ 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
SIGTERMwhen 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; usekeytool+ 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.
FAQ
What is 'rolling deployment'?
It's a way to update a program by gradually replacing old versions with new ones, ensuring the service never stops working.
What is 'blue-green deployment'?
It's a technique where you have two identical environments. One is live (blue) and the other is ready to receive traffic (green). The switch is instantaneous, allowing for quick rollbacks if needed.
Why shouldn't I use the ':latest' tag in Docker?
Using ':latest' can cause confusion and make it difficult to identify exactly which version is being used or rolled back. It's better to use specific tags, like 'node:22-alpine'.
Details
Original description by the author
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.
repo: github/awesome-copilot
Popularity
- GitHub stars
- 40k
- Ranking position
- #5159
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
acquire-codebase-knowledge
Helps your agent understand and document an existing code project. It's useful for onboarding new people or getting an overview of the architecture.
github/awesome-copilot
acreadiness-assess
Enables your agent to assess a project's readiness for AI and generate a report. It's useful for understanding how well a project is prepared to use AI tools.
github/awesome-copilot
acreadiness-generate-instructions
Helps your agent create instructions for AI tools based on an assessment. It's useful for improving how AI interacts with code and closing identified gaps.
github/awesome-copilot
acreadiness-policy
Enables your agent to help define or apply policies for AI project assessment. It's useful for standardizing how projects are evaluated and ensuring compliance.
github/awesome-copilot
Similar skills
bun-runtime
Has your agent use Bun to run, organize, and test code. It helps choose Bun over other tools and migrate existing projects.
affaan-m/ECC
database-migrations
Helps your agent make safe changes to databases. It ensures changes can be undone and minimizes downtime.
affaan-m/ECC
deployment-patterns
Sets up deployment and CI/CD workflows, containerization, and rollback strategies to ensure safe releases.
affaan-m/ECC