AutoGineer
Generated banner for Gem Devops Guidelines
Generated logo for Gem Devops Guidelines

Gem Devops Guidelines

GitHubOfficialFirst committed by mubaidrDistributed by GitHub

  • Skill
  • Guidelines
  • Cloud and DevOps
  • MIT
  • No issues found
Download ZIP

From 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.
— the description by mubaidr

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured framework for managing the full lifecycle of software deployments. It covers essential DevOps practices including infrastructure design, containerization, Kubernetes configuration, CI/CD pipeline structure, and mobile release management. The guidelines emphasize safety through rollback planning, health monitoring, and environment-specific configurations, ensuring production readiness across various platforms.

What it does

  • Provides a six-step workflow for planning and executing deployments safely.
  • Outlines best practices for Docker builds and Kubernetes probe configurations.
  • Defines standard CI/CD pipeline stages from pull request to production.
  • Offers checklists for pre-deployment, post-deployment, and production readiness.
  • Details specific strategies for feature flag management and lifecycle.
  • Covers mobile release procedures using industry-standard tools for iOS and Android.

When to use it

  • When designing or reviewing infrastructure and deployment pipelines.
  • When setting up containerized environments or Kubernetes workloads.
  • When establishing production readiness standards for new services.
  • When planning mobile application release and update strategies.
  • When defining rollback procedures and health check requirements.

Advantages

  • Promotes consistent, repeatable deployment processes.
  • Reduces risk through mandatory rollback planning and validation gates.
  • Encourages secure configuration management by avoiding hard-coded secrets.
  • Provides clear, actionable checklists for complex release scenarios.
  • Supports zero-downtime strategies like rolling, blue-green, and canary deployments.

Usage examples

“How should I structure my CI/CD pipeline for a new web service?”
The agent will outline a pipeline starting with linting, type checking, and unit tests for pull requests, followed by build, staging, smoke tests, and production deployment for the main branch.
“What are the best practices for Dockerizing my application?”
The agent will recommend using multi-stage builds, non-root users, pinning base images by digest, and defining health checks and resource limits.
“How do I manage feature flags safely?”
The agent will provide a lifecycle strategy including phased rollouts, owner assignment, expiration dates, and a requirement to remove dead code within two weeks.
“What should I include in my production readiness checklist?”
The agent will list requirements such as passing tests, JSON logging, meaningful health endpoints, pinned versions, resource limits, and a tested rollback plan.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/github/gem-devops-guidelines/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip gem-devops-guidelines.zip -d .agents/skills

Documentation by mubaidr

DevOps Guidelines

When to Use

Use for DevOps, platform, container, pipeline, or release tasks - any work that touches infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, or mobile release workflows.

Numbered Workflow

  1. Assess - identify workload type, target provider/environment, acceptance criteria, and risk level.

  2. Classify - select applicable sections (deployment strategy, Docker, K8s, CI/CD, health, config, rollback, feature flags, mobile) based on workload/provider/environment.

  3. Plan - for each selected section, define concrete steps, validation checks, and rollback triggers.

  4. Apply - execute the plan, running validation at each gate (lint -> typecheck -> unit -> integration -> preview -> smoke).

  5. Verify - confirm health endpoints, monitoring, rollback capability, and documented outcome.

  6. Rollback-ready - ensure a tested rollback path exists before declaring success.

Edge Cases

  • Idempotent re-run: workflow must be safe to execute multiple times without side effects.

  • Missing credentials: fail fast with clear error; never proceed with partial auth.

  • Workload without health endpoint: deploy but flag as incomplete; require health endpoint before production promotion.

  • Image digest pinning: always pin by digest (image@sha256:...) not tag for production.

  • Phased rollout rollback: if canary/blue-green rollout fails, revert traffic split instantly; do not wait for full rollback.

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, 2x 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.

Files

LICENSE

MIT License

Copyright GitHub, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Requirements and compatibility

Written for: GitHub Copilot

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Node.js

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

First committed by
GitHub avatar of mubaidrmubaidr
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · skills/gem-devops-guidelines · commit 797337f
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
mubaidr

AutoGineer is not affiliated with or endorsed by mubaidr or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download gem-devops-guidelines.zip