CI/CD & Release Engineering

"Ship small, ship often, and always know how to un-ship." [INFERENCE]

TL;DR

Designs CI/CD and release engineering: pipeline architecture (DAG, caching, parallelism), multi-environment strategy (staging/canary/prod parity), rollback (blue-green/canary), code-quality gates, dependency governance, and git-hook automation. Makes delivery fast, repeatable, and reversible. [EXPLICIT]

When to use

• Designing a CI pipeline (jobs, dependencies, caching, triggers). [EXPLICIT]
• Planning environments (staging/canary/prod parity, secrets, drift). [EXPLICIT]
• Choosing a rollback strategy (blue-green, canary, version pinning). [EXPLICIT]
• Adding quality gates (lint/format/test) and dependency governance. [EXPLICIT]
• Automating git hooks (pre-commit/pre-push/commit-msg). [EXPLICIT]

Sub-capabilities (resource map)

Procedure

1. Model the pipeline as a DAG; cache deps; parallelize independent jobs. [DOC]
2. Gate merges on lint + tests + security checks (fail fast). [INFERENCE]
3. Promote through environments with parity; scope secrets per environment. [DOC]
4. Make deploys reversible: blue-green or canary, with a defined rollback trigger. [DOC]
5. Govern dependencies: lockfiles, scheduled upgrades, security patching. [DOC]

Quality Criteria

• Pipeline caches deps and parallelizes; fails fast. [INFERENCE]
• Merge gated on lint + tests (+ security). [DOC]
• Environments parity-checked; secrets scoped, no drift. [DOC]
• Every deploy has a defined rollback path. [DOC]
• Claims evidence-tagged. [EXPLICIT]

Anti-Patterns

• Deploy with no rollback plan (forward-only fixes under pressure). [INFERENCE]
• Snowflake environments (works in staging, breaks in prod). [DOC]
• Unpinned dependencies (irreproducible builds). [DOC]

Contract

• Aceptación: pipeline DAG con cache/paralelismo y fail-fast; merge gated; entornos con parity y secrets por entorno; rollback definido; deps gobernadas. [EXPLICIT]
• Límites: ingeniería de entrega; no es observabilidad runtime (observability-operations) ni deploy específico de plataforma (lo consumen vercel/firebase/hostinger-platform). [EXPLICIT]
• Casos borde: migraciones de datos en rollback (no siempre reversibles) → plan de compatibilidad hacia atrás. [INFERENCE]
• Supuestos: repo con runner CI disponible (GitHub Actions u otro). [SUPUESTO]
• Trade-off: gates estrictos frenan merges a cambio de menos defectos en producción. [EXPLICIT]

Related Skills

• hook-engineering — Claude Code hooks parallel to git hooks. [EXPLICIT]
• observability-operations — deploy events feed monitoring. [EXPLICIT]
• vercel-platform, firebase-platform, hostinger-platform — deploy targets. [EXPLICIT]

Packet

Capas del packet, cargables bajo demanda (disciplina ICM: una capa por vez, nunca todas juntas): references/ guías de profundidad (cargar UNA por etapa) · knowledge/ cuerpo de conocimiento · prompts/ prompts listos · examples/ salida de ejemplo · agents/ subagentes del packet · assets/ recursos estáticos.