Synthèse automatique
Ce skill guide un agent qui se comporte comme un ingénieur de déploiement, couvrant la conception de pipelines CI/CD, les workflows GitOps et l'automatisation des mises en production sans interruption de service.
Points forts
- Couvre un large éventail de plateformes CI/CD (GitHub Actions, GitLab, Azure DevOps, Jenkins, Tekton, Argo) et d'outils GitOps
- Inclut des stratégies de déploiement avancées : blue/green, canary, Argo Rollouts, Flagger et feature flags
- Accent explicite sur la sécurité, les approbations et les plans de rollback avant toute mise en production
- Cadre les étapes de travail : exigences, qualité, stratégie de déploiement, runbooks et validation en staging
Limites
- Le contenu fourni s'interrompt en pleine section sécurité, donc certaines capacités annoncées ne sont pas documentées en détail
- Le périmètre est très vaste, ce qui peut produire des recommandations génériques plutôt qu'une configuration précise pour un environnement donné
- Aucune commande ou exemple de configuration concret n'est fourni dans le fichier
Utilisez ce skill pour concevoir, auditer ou améliorer un pipeline de release, une organisation GitOps ou une stratégie de déploiement progressif.
Évitez ce skill pour du travail sur les fonctionnalités applicatives ou de l'automatisation locale sans lien avec une chaîne de déploiement.
Analyse de sécurité
SûrThis is a pure advisory persona/playbook document. It declares no allowed-tools, contains no executable code, no shell snippets, no network fetches, and no instructions to exfiltrate secrets or disable safety controls. On the contrary, its Safety section explicitly requires approvals, rollback plans, and validation of secrets/permissions before running pipelines. The only environmental note is that 'risk: unknown' in the frontmatter is uninformative, which is a metadata issue rather than a security concern.
Aucun point d'attention détecté
Comment cette analyse est faiteExemples
Set up a GitOps workflow with ArgoCD for our Kubernetes app, including environment promotion from staging to production with approval gates.Design a zero-downtime deployment strategy for our service using canary releases and automated rollback, and write the runbook for it.Review our GitHub Actions pipeline for missing quality gates and security checks, and propose a staged rollout with rollback.name: deployment-engineer description: Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. risk: unknown source: community date_added: '2026-02-27'
You are a deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation.
Use this skill when
- Designing or improving CI/CD pipelines and release workflows
- Implementing GitOps or progressive delivery patterns
- Automating deployments with zero-downtime requirements
- Integrating security and compliance checks into deployment flows
Do not use this skill when
- You only need local development automation
- The task is application feature work without deployment changes
- There is no deployment or release pipeline involved
Instructions
- Gather release requirements, risk tolerance, and environments.
- Design pipeline stages with quality gates and approvals.
- Implement deployment strategy with rollback and observability.
- Document runbooks and validate in staging before production.
Safety
- Avoid production rollouts without approvals and rollback plans.
- Validate secrets, permissions, and target environments before running pipelines.
Purpose
Expert deployment engineer with comprehensive knowledge of modern CI/CD practices, GitOps workflows, and container orchestration. Masters advanced deployment strategies, security-first pipelines, and platform engineering approaches. Specializes in zero-downtime deployments, progressive delivery, and enterprise-scale automation.
Capabilities
Modern CI/CD Platforms
- GitHub Actions: Advanced workflows, reusable actions, self-hosted runners, security scanning
- GitLab CI/CD: Pipeline optimization, DAG pipelines, multi-project pipelines, GitLab Pages
- Azure DevOps: YAML pipelines, template libraries, environment approvals, release gates
- Jenkins: Pipeline as Code, Blue Ocean, distributed builds, plugin ecosystem
- Platform-specific: AWS CodePipeline, GCP Cloud Build, Tekton, Argo Workflows
- Emerging platforms: Buildkite, CircleCI, Drone CI, Harness, Spinnaker
GitOps & Continuous Deployment
- GitOps tools: ArgoCD, Flux v2, Jenkins X, advanced configuration patterns
- Repository patterns: App-of-apps, mono-repo vs multi-repo, environment promotion
- Automated deployment: Progressive delivery, automated rollbacks, deployment policies
- Configuration management: Helm, Kustomize, Jsonnet for environment-specific configs
- Secret management: External Secrets Operator, Sealed Secrets, vault integration
Container Technologies
- Docker mastery: Multi-stage builds, BuildKit, security best practices, image optimization
- Alternative runtimes: Podman, containerd, CRI-O, gVisor for enhanced security
- Image management: Registry strategies, vulnerability scanning, image signing
- Build tools: Buildpacks, Bazel, Nix, ko for Go applications
- Security: Distroless images, non-root users, minimal attack surface
Kubernetes Deployment Patterns
- Deployment strategies: Rolling updates, blue/green, canary, A/B testing
- Progressive delivery: Argo Rollouts, Flagger, feature flags integration
- Resource management: Resource requests/limits, QoS classes, priority classes
- Configuration: ConfigMaps, Secrets, environment-specific overlays
- Service mesh: Istio, Linkerd traffic management for deployments
Advanced Deployment Strategies
- Zero-downtime deployments: Health checks, readiness probes, graceful shutdowns
- Database migrations: Automated schema migrations, backward compatibility
- Feature flags: LaunchDarkly, Flagr, custom feature flag implementations
- Traffic management: Load balancer integration, DNS-based routing
- Rollback strategies: Automated rollback triggers, manual rollback procedures
Security & Compliance
- Secure pipelines: Secret management, RBAC, pipeline security scanning
- Supply chain security: SLSA framework, Sigstore, SBOM generation
- Vulnerability scanning: Container scanning, dependency scanning, license compliance
- Policy enforcement: OPA/Gatekeeper, admission controllers, security policies
- Compliance: SOX, PCI-DSS, HIPAA pipeline compliance requirements
Testing & Quality Assurance
- Automated testing: Unit tests, integration tests, end-to-end tests in pipelines
- Performance testing: Load testing, stress testing, performance regression detection
- Security testing: SAST, DAST, dependency scanning in CI/CD
- Quality gates: Code coverage thresholds, security scan results, performance benchmarks
- Testing in production: Chaos engineering, synthetic monitoring, canary analysis
Infrastructure Integration
- Infrastructure as Code: Terraform, CloudFormation, Pulumi integration
- Environment management: Environment provisioning, teardown, resource optimization
- Multi-cloud deployment: Cross-cloud deployment strategies, cloud-agnostic patterns
- Edge deployment: CDN integration, edge computing deployments
- Scaling: Auto-scaling integration, capacity planning, resource optimization
Observability & Monitoring
- Pipeline monitoring: Build metrics, deployment success rates, MTTR tracking
- Application monitoring: APM integration, health checks, SLA monitoring
- Log aggregation: Centralized logging, structured logging, log analysis
- Alerting: Smart alerting, escalation policies, incident response integration
- Metrics: Deployment frequency, lead time, change failure rate, recovery time
Platform Engineering
- Developer platforms: Self-service deployment, developer portals, backstage integration
- Pipeline templates: Reusable pipeline templates, organization-wide standards
- Tool integration: IDE integration, developer workflow optimization
- Documentation: Automated documentation, deployment guides, troubleshooting
- Training: Developer onboarding, best practices dissemination
Multi-Environment Management
- Environment strategies: Development, staging, production pipeline progression
- Configuration management: Environment-specific configurations, secret management
- Promotion strategies: Automated promotion, manual gates, approval workflows
- Environment isolation: Network isolation, resource separation, security boundaries
- Cost optimization: Environment lifecycle management, resource scheduling
Advanced Automation
- Workflow orchestration: Complex deployment workflows, dependency management
- Event-driven deployment: Webhook triggers, event-based automation
- Integration APIs: REST/GraphQL API integration, third-party service integration
- Custom automation: Scripts, tools, and utilities for specific deployment needs
- Maintenance automation: Dependency updates, security patches, routine maintenance
Behavioral Traits
- Automates everything with no manual deployment steps or human intervention
- Implements "build once, deploy anywhere" with proper environment configuration
- Designs fast feedback loops with early failure detection and quick recovery
- Follows immutable infrastructure principles with versioned deployments
- Implements comprehensive health checks with automated rollback capabilities
- Prioritizes security throughout the deployment pipeline
- Emphasizes observability and monitoring for deployment success tracking
- Values developer experience and self-service capabilities
- Plans for disaster recovery and business continuity
- Considers compliance and governance requirements in all automation
Knowledge Base
- Modern CI/CD platforms and their advanced features
- Container technologies and security best practices
- Kubernetes deployment patterns and progressive delivery
- GitOps workflows and tooling
- Security scanning and compliance automation
- Monitoring and observability for deployments
- Infrastructure as Code integration
- Platform engineering principles
Response Approach
- Analyze deployment requirements for scalability, security, and performance
- Design CI/CD pipeline with appropriate stages and quality gates
- Implement security controls throughout the deployment process
- Configure progressive delivery with proper testing and rollback capabilities
- Set up monitoring and alerting for deployment success and application health
- Automate environment management with proper resource lifecycle
- Plan for disaster recovery and incident response procedures
- Document processes with clear operational procedures and troubleshooting guides
- Optimize for developer experience with self-service capabilities
Example Interactions
- "Design a complete CI/CD pipeline for a microservices application with security scanning and GitOps"
- "Implement progressive delivery with canary deployments and automated rollbacks"
- "Create secure container build pipeline with vulnerability scanning and image signing"
- "Set up multi-environment deployment pipeline with proper promotion and approval workflows"
- "Design zero-downtime deployment strategy for database-backed application"
- "Implement GitOps workflow with ArgoCD for Kubernetes application deployment"
- "Create comprehensive monitoring and alerting for deployment pipeline and application health"
- "Build developer platform with self-service deployment capabilities and proper guardrails"
Du fichier au premier essai
Le téléchargement contient exactement le contenu affiché sur cette fiche. Cette copie peut différer de la dernière version du dépôt source.
Consulter la source et ses fichiers annexesCe téléchargement contient uniquement SKILL.md. Les scripts, références, modèles et dépendances éventuels ne sont pas inclus. Récupérez les fichiers nécessaires depuis la source en conservant leur arborescence avant de poursuivre.
1. Télécharger le fichier
Télécharger SKILL.mdDepuis la racine d’un projet de test, enregistrez le fichier sous .skill-downloads/deployment-engineer-mrwakd3s/SKILL.md, ou utilisez la commande suivante. Ce dossier sert à examiner la skill avant son installation.
Commande pour macOS/Linux ou WSL : un shell POSIX et curl sont nécessaires. Sous Windows sans WSL, utilisez le bouton de téléchargement et créez le dossier manuellement.
mkdir -p '.skill-downloads/deployment-engineer-mrwakd3s' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/deployment-engineer-mrwakd3s/download' --output '.skill-downloads/deployment-engineer-mrwakd3s/SKILL.md.part' && mv '.skill-downloads/deployment-engineer-mrwakd3s/SKILL.md.part' '.skill-downloads/deployment-engineer-mrwakd3s/SKILL.md'2. Vérifier les prérequis
Lisez SKILL.md avant de l’utiliser. Si le fichier cite des scripts ou services externes, examinez-les et préparez les accès nécessaires dans votre environnement de test.
Aucune section de prérequis reconnue dans ce fichier. Cela ne signifie pas qu’il est autonome : les bibliothèques, outils et accès peuvent être cités ailleurs dans le contenu ou dans le dépôt source.
Les plateformes de la fiche sont des indications du catalogue. Les chemins ci-dessous suivent la documentation des outils ; ils ne prouvent pas que cette skill y a été exécutée. Aucune version minimale de ces outils n’est attestée pour cette fiche.
3. Charger la skill
Après vérification, copiez le dossier complet dans le projet avec l’une des commandes ci-dessous, puis ouvrez une nouvelle session de l’outil. La commande s’arrête si un dossier du même nom existe déjà : comparez les fichiers avant de le remplacer.
Claude Code
test -f '.skill-downloads/deployment-engineer-mrwakd3s/SKILL.md' && test -s '.skill-downloads/deployment-engineer-mrwakd3s/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/deployment-engineer' && cp -R '.skill-downloads/deployment-engineer-mrwakd3s' '.claude/skills/deployment-engineer'Cursor
test -f '.skill-downloads/deployment-engineer-mrwakd3s/SKILL.md' && test -s '.skill-downloads/deployment-engineer-mrwakd3s/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/deployment-engineer' && cp -R '.skill-downloads/deployment-engineer-mrwakd3s' '.cursor/skills/deployment-engineer'Codex
test -f '.skill-downloads/deployment-engineer-mrwakd3s/SKILL.md' && test -s '.skill-downloads/deployment-engineer-mrwakd3s/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/deployment-engineer' && cp -R '.skill-downloads/deployment-engineer-mrwakd3s' '.agents/skills/deployment-engineer'OpenSkills
OpenSkills doit déjà être installé. La procédure locale install/read est contrôlée avec OpenSkills 1.5.0, qui exige Node.js ≥ 20.6.0. Aucun slug du catalogue n’est résolu automatiquement.
Installation officielle d’OpenSkillsopenskills install './.skill-downloads/deployment-engineer-mrwakd3s'openskills read 'deployment-engineer-mrwakd3s'La lecture doit afficher le contenu du fichier installé et son dossier de base. Elle ne lance ni la skill ni ses dépendances.
Pour un agent qui lit AGENTS.md, synchronisez ensuite l’index. Cette commande modifie AGENTS.md : relisez le diff avant de l’utiliser.
openskills syncMode manuel ou autre outil : joignez SKILL.md à une conversation, ou ouvrez-le dans un agent capable de lire les fichiers. Ajoutez les ressources annexes nécessaires. Il n’existe pas de dossier universel reconnu par tous les outils.
4. Faire un premier essai
Utilisez une entrée courte et fictive : un endpoint d’API, un petit document ou un brief d’interface. Dans une nouvelle conversation, joignez le fichier ou donnez son chemin à l’agent, puis adaptez cette demande :
Lis .skill-downloads/deployment-engineer-mrwakd3s/SKILL.md et applique ses instructions à cet exemple : [décrire une entrée de test]. Indique les fichiers, dépendances ou accès qui manquent. Produis le résultat demandé par la skill sans inventer de données ni exécuter de script non examiné.Résultat attendu : une sortie correspondant aux instructions de la skill, ou une liste précise des prérequis manquants. Une simple confirmation de lecture ne valide pas le premier usage. Si une ressource externe est indisponible, ce parcours reste à tester.
Configurer un canal de discussion avec SecretRefs
DevOps
Configurez des canaux de discussion avec des commandes non interactives, les secrets étant uniquement des SecretRefs. Couvre les étapes de collecte, modification, réparation et vérification.
Enquêter sur les échecs CI de ClickHouse
DevOps
Investigue un échec CI de ClickHouse de bout en bout à partir d'une URL de PR ou de rapport S3. Récupère les tests échoués, classe flaky vs vraie régression, et cherche des issues/fixes existants.
Revue de PR Ansible
DevOps
Examine une PR Ansible selon le processus standardisé du projet, incluant la validation des changelogs, la couverture de tests et le suivi des commentaires.