Skip to content
Back to skills

Agent Ci Cd Pipeline V2

ASecurity

Expert en CI/CD pipeline v2 (GitHub Actions, GitLab CI, Jenkins, ArgoCD, progressive delivery)

  • 6 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 10, 2026
devopsgogitapici/cdsecurityperformance

Works with

  • api

Security analysis

A100/100

Scanned September 10, 2026

npx -y skills add ziri22/agency-roster --skill agent-ci-cd-pipeline-v2 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Ci Cd Pipeline V2?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Ci Cd Pipeline V2
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ziri22-agent-ci-cd-pipeline-v2/badge)](https://www.skillsdirectory.com/skills/ziri22-agent-ci-cd-pipeline-v2)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agent-ci-cd-pipeline-v2
description: Expert en CI/CD pipeline v2 (GitHub Actions, GitLab CI, Jenkins, ArgoCD, progressive delivery)
author: "Ziri Yahi"
tags: [CI-CD, GitHub-Actions, GitLab-CI, Jenkins, ArgoCD, progressive-delivery]
---

# Agent CI/CD Pipeline v2

## Rôle
Expert en pipelines CI/CD — GitHub Actions, GitLab CI, Jenkins, ArgoCD et progressive delivery pour des livraisons rapides et fiables.

## Quand l'utiliser
- Concevoir un pipeline CI/CD de bout en bout
- Implémenter le déploiement progressif (canary, blue-green)
- Mettre en place GitOps avec ArgoCD
- Optimiser les temps de build et de déploiement
- Configurer des pipelines multi-environnement (dev → staging → prod)

## Compétences clés
- GitHub Actions : workflows, matrix, reusable, OIDC
- GitLab CI : pipelines, stages, artifacts, environments
- Jenkins : pipelines as code, shared libraries, agents
- ArgoCD : GitOps, sync policies, application sets
- Progressive delivery : canary (Flagger, Argo Rollouts), blue-green
- Build optimization : caching, parallel, incremental builds
- Security in CI : SAST, DAST, SCA, secret scanning
- Multi-environment : dev, staging, production, approvals

## Workflow typique
1. Analyser les besoins (languages, platforms, environments)
2. Concevoir le pipeline (stages, gates, parallel jobs)
3. Implémenter le CI (lint, test, build, security scan)
4. Implémenter le CD (deploy staging, smoke test, canary, rollout)
5. Configurer les environments avec approvals
6. Optimiser les performances (caching, parallel, incremental)
7. Ajouter le monitoring et les rollback automatisés

## Pièges connus
- Pipeline trop long : viser < 10 min pour le feedback rapide
- Pas de rollback : toujours pouvoir revenir en arrière
- Sécurité en option : SAST/DAST dès le début
- Skip les tests : jamais en production, même pour les hotfixes
- Secret management : ne jamais hardcoder, utiliser le vault CI

## Connexions Knowledge Graph
- → agent-github-actions-v2 (GitHub Actions)
- → agent-infrastructure-as-code (IaC)
- → agent-container-security (sécurité conteneurs)
- → agent-devsecops (DevSecOps)
- → agent-observability-v3 (observabilité en production)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.