ci-cd-pipeline-patterns_skill

Overview

This skill provides a practical catalog of CI/CD pipeline patterns focused on GitHub Actions, workflow design, automation, testing, deployment strategies, and release management. It distills patterns and examples for building reliable, secure, and fast delivery pipelines for modern applications. Use it to design end-to-end pipelines, optimize runtime, and standardize release processes across teams.

How this skill works

The skill inspects and codifies common CI/CD building blocks: workflows, jobs, steps, actions, secrets, artifacts, and triggers. It maps testing strategies (unit, integration, e2e, performance) to pipeline jobs, shows matrix and caching patterns for speed, and documents deployment strategies (blue-green, canary, rolling) with rollout and rollback steps. It also covers best practices for secrets, environments, reusable workflows, and multi-platform matrix builds.

When to use it

• Setting up CI/CD for a new project using GitHub Actions
• Automating builds, tests, and deployments across staging and production
• Implementing multi-platform matrix builds or monorepo pipelines
• Securing pipelines with scoped secrets, OIDC, and environment protections
• Optimizing pipeline performance with caching, artifacts, and parallel jobs
• Designing safe rollouts using blue-green, canary, or rolling deployments

Best practices

• Keep workflows small and single-purpose; use reusable workflow_call for shared logic
• Scope secrets to environments and prefer OIDC or short-lived credentials
• Use matrix builds with fail-fast disabled for broader test feedback when needed
• Cache dependencies and Docker layers to reduce build time and runner costs
• Publish artifacts and test reports for traceability and post-failure analysis
• Automate semantic versioning, changelog generation, and gated releases

Example use cases

• A Node.js project: CI pipeline with lint, unit tests, coverage upload, and Docker image build
• A microservices platform: integration tests using service containers and contract checks
• A web app: E2E Playwright tests and Lighthouse performance checks before deployment
• Progressive delivery: canary rollout to 10% traffic with metric-based promotion to 100%
• Monorepo: targeted builds and caching per package with reusable workflows for each team