ci-cd
Skill1 starsChanged 4 months agoMITView on GitHub
Integração e entrega contínuas production-grade: pipelines rápidos e confiáveis, trunk-based development, feature flags, e estratégias de deploy (blue-green, canary, rolling) com rollback. Use quando o usuário mencionar: "CI/CD", "pipeline", "GitHub Actions", "deploy", "trunk-based", "feature flag", "canary", "blue-green", "rollback", "release", "build automatizado", "esteira".
38 other projects use a version of this.
Adopted by
Most recently taken up by
- codewithmukesh/dotnet-claude-kittheir own version, first seen Nov 8, 2026
- Mehul72/skillstheir own version, first seen Nov 8, 2026
- AsiaOstrich/EngramGraphtheir own version, first seen Nov 8, 2026
- celestialdust/achilles-skillstheir own version, first seen Nov 1, 2026
- scoobydont-666/shared-claude-skillstheir own version, first seen Nov 1, 2026
- MiguelSavignano/claude-code-systemtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use caching, api-versioning and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
wpankSkillcaching
Caching strategies, invalidation, eviction policies, HTTP caching, distributed caching, and anti-patterns. Use when designing cache layers, choosing eviction policies, debugging stale data, or optimizing read-heavy workloads.
Also in 5 projects that use this
- wpankSkill
api-versioning
API versioning strategies — URL path, header, query param, content negotiation — with breaking change classification, deprecation timelines, migration patterns, and multi-version support. Use when evolving APIs, planning breaking changes, or managing version lifecycles.
Also in 3 projects that use this
SentrySkillfeature-flags
Gate a Sentry feature behind a FlagPole feature flag. Use when adding a feature flag, registering a flag in temporary.py, checking a flag from Python or the frontend, enabling a flag in tests, or asking where FlagPole rollout config lives. Trigger on "add a feature flag", "gate this behind a flag", "register a flag", "features.has", "api_expose", "OrganizationFeature", "ProjectFeature", "FlagPole".
Also in 4 projects that use this
OpenAISkillauth
Authentication integration guidance — Clerk (native Vercel Marketplace), Descope, and Auth0 setup for Next.js applications. Covers middleware auth patterns, sign-in/sign-up flows, and Marketplace provisioning. Use when implementing user authentication.
Also in 4 projects that use this
wrsmith108Skilldocker
Container-based development for isolated, reproducible environments. Use when running npm commands, installing packages, executing code, or managing project dependencies. Trigger phrases include "npm install", "run the build", "start the server", "install package", or any code execution request.
Also in 9 projects that use this
mylee04Skillshell-scripting
Shell scripting best practices for cross-platform CLI tools
Also in 3 projects that use this
Other versions38 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 38
- cunarist/rinf★ 2.8ksame name
- codewithmukesh/dotnet-claude-kit★ 808same name
- Resgrid/Core★ 238same name
- kid-sid/claude-spellbook★ 190same name
- irahardianto/awesome-agv★ 157same name
- AsiaOstrich/universal-dev-standards★ 84same name
- nahid-sparktales/agent-dispatcher★ 59same name
- mgifford/accessibility-skills★ 48same name
- nimadorostkar/Claude-Skills-collection★ 33same name
- iuliandita/skills★ 11same name
28 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository70 other files it gives its agents.
- agent-creationSkill
- handoffSkill
- task-distributorSkill
- task-plannerSkill
- accessibilitySkill
- airbnb-designSkill
- airtable-designSkill
- atlassian-designSkill
- carbon-designSkill
- cloudscape-designSkill
- coinbase-designSkill
- discord-designSkill
- duolingo-designSkill
- figma-designSkill
- fluent-designSkill
- linear-designSkill
- material-designSkill
- meta-designSkill
- netflix-designSkill
- notion-designSkill
- nubank-designSkill
- one-ui-designSkill
- pinterest-designSkill
- polaris-designSkill
- premium-web-designSkill
- primer-designSkill
- reddit-designSkill
- revolut-designSkill
- robinhood-designSkill
- salesforce-lightning-designSkill
- slack-designSkill
- spectrum-designSkill
- spotify-designSkill
- stripe-designSkill
- tiktok-designSkill
- twitch-designSkill
- uber-base-designSkill
- vercel-geist-designSkill
- visionos-designSkill
- whatsapp-designSkill
- economicsSkill
- legal-basicsSkill
- negotiationSkill
- politicalSkill
- api-designSkill
- architectureSkill
- caching-strategiesSkill
- database-designSkill
- event-drivenSkill
- observabilitySkill
- payment-systemsSkill
- performanceSkill
- qaSkill
- refactoringSkill
- securitySkill
- system-designSkill
- testingSkill
- clone-websiteSkill
- graphifySkill
- remotionSkill
- The first 60 shown.
The file
Files
CI/CD
Você atua como engenheiro de plataforma/DevEx. Objetivo: transformar "commit" em "em produção com segurança" de forma rápida, automática e reversível. Feedback veloz e deploys pequenos e frequentes reduzem risco — o contrário do que a intuição diz.
Princípios
- Build once, deploy many — gere o artefato uma vez; promova o mesmo binário/imagem por dev→staging→prod. Nunca rebuilde por ambiente (config vem de fora).
- Feedback rápido — pipeline em minutos, não horas. Etapas rápidas primeiro (lint/unit) para falhar cedo; caras depois (e2e).
- Deploys pequenos e frequentes — lote pequeno = risco pequeno e diagnóstico fácil. Big bang mensal é o antipadrão.
- Tudo reversível — todo deploy tem rollback testado (ou feature flag para desligar). Nunca vá para prod sem saída.
- Pipeline como código — versionado no repo, revisável, reproduzível.
CI — o pipeline
# Ordem por custo (rápido/barato → lento/caro): falhe cedo
stages:
- lint + format # segundos
- typecheck # segundos
- unit tests # segundos-minutos
- build (artefato único)
- integration tests # minutos
- security scan (SCA/SAST) # ver [[security]]
- e2e (só fluxos críticos) # mais lentoRegras: pipeline verde é obrigatório para merge; flaky test é bloqueador (conserte ou quarentena, ver [[testing]]); cache de dependências para velocidade; roda em todo PR.
Trunk-based development
- Todos integram numa
mainsempre deployável, várias vezes ao dia. - Branches curtas (horas/1-2 dias), PRs pequenos.
- Trabalho incompleto fica escondido atrás de feature flag, não numa branch longa.
- Evita "merge hell" e integra cedo (onde bugs são baratos).
Feature flags (desacopla deploy de release)
Deploy (código em prod, desligado) ≠ Release (ligado para usuários)- Solte código escondido; ligue por %/segmento quando pronto.
- Kill switch: desligue um recurso problemático sem redeploy.
- Testes em produção (canary por flag), rollout gradual.
- Higiene: remova flags mortas (dívida técnica se acumulam).
Estratégias de deploy
| Estratégia | Como | Quando |
| Rolling | Substitui instâncias aos poucos | Default, simples |
| Blue-green | Sobe ambiente novo (green) completo, troca o tráfego, mantém o antigo (blue) para rollback instantâneo | Rollback rápido, custo de 2x infra |
| Canary | Manda 1%→10%→100% do tráfego para a versão nova, observando métricas | Alto risco, quer validar em prod com pouca exposição |
Sempre com health checks e rollback automático se erro/latência subir (liga com [[observability]] — deploy observa SLO).
Fluxo ideal
commit → CI (verde) → merge na main → build artefato → deploy staging (auto)
→ smoke tests → deploy prod (canary) → observa SLO → 100% ou rollbackRecursos externos
| Recurso | O que pegar |
| Continuous Delivery (Jez Humble/Farley) | Fundamentos: build once, pipeline, deploy pequeno. |
| Trunk Based Development | Como integrar continuamente sem branches longas. |
| GitHub Actions Docs | Escrever workflows de CI/CD. |
| DORA Metrics (Google) | Deploy frequency, lead time, MTTR, change fail rate. |
| Martin Fowler — Feature Flags | Tipos de flag e higiene. |
| Argo Rollouts / Flagger | Canary/blue-green automatizado (k8s). |
Do / Don't
| Do | Don't |
| Build once, promova o artefato | Rebuild por ambiente |
| Deploys pequenos e frequentes | Big bang mensal |
| Feature flag para esconder incompleto | Branch de vida longa |
| Rollback/kill switch testado | Deploy sem saída |
| Falhar cedo (rápido antes de caro) | e2e antes de unit |
Checklist
- Pipeline como código, verde obrigatório para merge
- Etapas ordenadas por custo (falha cedo)
- Artefato único promovido por ambiente (config externa)
- Trunk-based + PRs pequenos + feature flags
- Estratégia de deploy escolhida (rolling/blue-green/canary) com health check
- Rollback/kill switch testado; deploy observa SLO
- Métricas DORA acompanhadas
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.