Verified:GitHub

cicd-patterns

Design CI/CD pipelines for GitHub Actions and GitLab CI with deployment strategies.

381|48|Updated Aug 12, 2025

Search Tags:#CI/CD #pipeline #quality gates #blue-green #canary

One-click install

npx skills add https://github.com/rsmdt/the-startup --skill cicd-patterns

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: cicd-patterns
Source: https://github.com/rsmdt/the-startup/tree/main/plugins/team/skills/infrastructure/cicd-patterns
Command: npx skills add https://github.com/rsmdt/the-startup --skill cicd-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides patterns for building CI/CD pipelines, deployment strategies, and quality gates.

Core Features & Use Cases

Pipeline architecture: Build, test, analyze, package, deploy, verify stages.
Deployment strategies: Blue/Green, Canary, Rolling.
Quality gates: Enforce tests and code quality before release.

Quick Start

Create a minimal CI/CD pipeline that builds, tests, and deploys to a staging environment.

Frequently Asked Questions about cicd-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design a CI/CD pipeline with multiple deployment stages?▼

CI/CD pipelines follow a standardized architecture: Build → Test → Analyze → Package → Deploy → Verify. Each stage enforces specific checks—tests validate functionality, code analysis ensures quality, and artifacts remain immutable throughout promotion across environments, creating a reliable path from code commit to production.

What's the difference between blue-green, canary, and rolling deployments?▼

Blue-green maintains two identical production environments, switching traffic instantly with zero downtime. Canary gradually routes traffic to a new version to detect issues early. Rolling replaces instances incrementally. Each suits different risk tolerances and rollback requirements; choose based on your tolerance for staged validation versus instant cutover.

How do quality gates prevent bad code from reaching production?▼

Quality gates are automated checkpoints that block deployment when tests fail, code quality thresholds aren't met, or security scans detect vulnerabilities. They enforce pass/fail criteria before the Package stage, stopping problematic builds early and reducing production incidents through fail-fast enforcement.

Can I implement CI/CD pipelines with GitHub Actions and GitLab CI?▼

Yes. Both GitHub Actions and GitLab CI support the complete pipeline architecture—Build, Test, Analyze, Package, Deploy, Verify—with quality gates, environment parity, artifact caching, and automated rollback. Implementation syntax differs, but core patterns remain consistent across both platforms.

What happens if a deployment fails—can it roll back automatically?▼

Automated rollback is built into resilient pipeline design. When the Verify stage detects issues in production, the pipeline can automatically revert to the previous immutable artifact, restoring the last known-good state without manual intervention or downtime.