Our review

Designs and optimizes CI/CD pipelines (GitHub Actions, GitLab CI) to automate testing, linting, building, and deployment.

Strengths

Offers three pipeline tiers (Scout, Guardian, Ironclad) tailored to project needs.
Automatically includes caching, secrets management, and matrix builds.
Supports multiple stacks (Python, Node, Go) with modern tooling.
Provides technical documentation in English for each pipeline.

Limitations

Does not cover advanced deployment strategies like canary or blue/green.
May require manual tweaks for unsupported stacks.
Relies on user input to choose the pipeline tier.

When to use it

Use this skill to quickly set up CI/CD workflows on GitHub Actions or GitLab CI, from simple linting to full deployment automation.

When not to use it

Do not use it for complex multi-cloud orchestration or pipelines requiring advanced rollback logic.

Examples

Basic PR pipeline

I need a GitHub Actions pipeline for a Python project using pytest and ruff. It should run on every PR and push to main, only linting and testing.

Full deploy pipeline

Set up a GitLab CI pipeline for a Node.js app with eslint and vitest, deploying to Vercel on tags. Include caching and secrets.

Optimize slow pipeline

My GitHub Actions pipeline takes 20 minutes. Can you optimize it with caching, matrix builds, and fail-fast strategy?

name: ci-cd-pilot description: > Diseña y optimiza pipelines de CI/CD — GitHub Actions, GitLab CI, automatización de tests, linting, builds y deploys. Trigger: Cuando hay que automatizar tests, linting, builds o deploys, o configurar un pipeline de CI/CD. license: MIT metadata: author: Leandro Benjamin L. version: "1.0"

Skill: ci-cd-pilot

Pipelines que no se rompen los viernes a las 18.

Trigger

Querés que los tests corran solos en cada PR
Necesitás automatizar el deploy a staging/prod
Hay que configurar linting + type checking en CI
Un pipeline existente tarda 20 minutos y hay que optimizarlo
Vas a mergear y querés que pase por controles automáticos

Workflow LEND

1. ANALIZAR
   ├── Stack: Python (ruff, pytest), Node (eslint, vitest), Go (golangci-lint)
   ├── ¿Hay tests? ¿Hay linter? ¿Hay type checker?
   ├── ¿Dónde deploya? (Railway, Vercel, AWS, Docker Hub)
   └── ¿Ambientes? (dev, staging, prod)

2. OFRECER (Menú del Senior)
   ├── A) Scout: lint + type check + build. Rápido, mínimo.
   ├── B) Guardian: lint + tests + build + security scan. No mergea si falla.
   └── C) Ironclad: todo + auto-deploy + notificaciones + matrix builds

3. ELEGIR → el usuario confirma

4. HACER
   ├── .github/workflows/main.yml o .gitlab-ci.yml
   ├── Secrets bien configurados (nunca hardcodeados)
   ├── Dependency caching (pip cache, npm cache, go mod cache)
   ├── Matrix builds si aplica (3.10, 3.11, 3.12)
   └── Documentación en inglés técnico del pipeline

5. VERIFICAR
   ├── El workflow corre sin errores
   ├── Los secrets están configurados en GitHub/GitLab
   └── El caché funciona (segundo run es más rápido)

Patrones

Caching: siempre cachear dependencias entre runs
Secrets: usar GitHub Secrets / GitLab CI variables, nunca en el yaml
Fail fast: primero lint, después tests, después build
Matrix: testear contra 2-3 versiones del runtime
Trigger condicional: CI en PRs y push a main; CD solo en tags o main
Notificaciones: solo fallos, no saturar con éxitos

Anti-patrones

Hardcodear API keys o tokens en el workflow yaml
CI que tira warning pero pasa igual (poné --error-on-warning)
Deploy automático sin pasar por PR
Un solo workflow de 500 líneas — partí en workflows reusables
Cachear sin key — la cache se vuelve obsoleta

CI/CD Pilot

Recommended for