JiayiV/question_mixing / skills/gem-devops-guidelines
gem-devops-guidelines
UnverifiedDesign 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
Deployment strategy
- Rolling (default): gradual, zero-downtime replacement.
- Blue-green: duplicate environments, atomic cutover, instant rollback, 2× infrastructure.
- Canary: route a small percentage first; requires traffic splitting.
Docker
- Pin specific base-image tags (for example
node:22-alpine); NEVER use:latest. - Use multi-stage builds and a non-root user. Copy dependencies first for caching.
.dockerignore:node_modules,.git, tests. DefineHEALTHCHECKand resource limits.
Kubernetes
Configure startup, readiness, and liveness probes with workload-appropriate initial delays and 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 and gracefully handle
SIGTERMwhen the workload requires it.
Configuration
Use environment variables (Twelve-Factor), separated by environment. Validate at startup and fail fast. NEVER commit secrets or hard-code NODE_ENV=production.
Rollback
Kubernetes: kubectl rollout undo. Vercel: vercel rollback. Docker: redeploy the previous pinned image.
Feature Flags
- Lifecycle: create → enable → 5% → 25% → 50% → 100% → remove flag and dead code.
- Every flag MUST have an owner, expiration, and rollback trigger. Remove within two weeks.
Checklists
- Pre-deploy, when applicable: passing tests, code review, environment variables, migrations, rollback plan.
- Post-deploy services: healthy, monitored, old pods terminated, outcome documented.
- Production services: passing tests; no hardcoded secrets; JSON logs; meaningful health; pinned versions; validated environment variables; 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. - Keep credentials in environment/secret storage, never Git. Automate iOS development/distribution signing with
fastlane match; usekeytooland Google Play App Signing for Android. - TestFlight: internal instant; external 90 days/100 testers. Google Play: internal/beta/production. Expect 1–7 days for review.
- Rollback: EAS
eas update:rollback; native release → revert build; store release → reduce phased rollout.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Unverified | Install |