How do I install the CI CD Pipeline Design skill?

Run npx skillmds add majiayu000/ci-cd-pipeline-design in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is CI CD Pipeline Design safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CI CD Pipeline Design?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is CI CD Pipeline Design free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Complete terms in LICENSE.

Who published CI CD Pipeline Design?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CI CD Pipeline Design by majiayu000

Name: CI CD Pipeline Design
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

CI/CD Pipeline Design

Version: 0.17.0

When to Use

Setting up CI/CD for new project
Optimizing pipeline performance
Adding security scanning
Designing multi-environment deployment

CI/CD Fundamentals

CI (Integration): Auto build/test on every change. Goal: Fast feedback (<10 min) CD (Delivery): Auto prepare releases. Goal: Always deployable main CD (Deployment): Auto deploy to production. Requires: High coverage, feature flags, monitoring

Pipeline Architectures

Linear

Build → Test → Security → Deploy

Best for: Simple projects

Parallel

Build → [Unit|Lint|SAST] → Deploy

Best for: Faster feedback

Multi-Environment

Build → Test → Staging → Approval → Production

Best for: Production deployments

Stage Design

Build

Cache dependencies, multi-stage builds, version artifacts

Test (Pyramid)

Few E2E (slow) → Some Integration → Many Unit (fast)

Security

Type	Tools
SAST	SonarQube, Semgrep, CodeQL
Dependencies	Snyk, Dependabot
Secrets	GitLeaks, TruffleHog
Containers	Trivy, Clair

Deploy

Staging: automatic
Production: manual approval, canary rollout

Deployment Strategies

Blue-Green

Deploy to inactive (Green), switch traffic, keep Blue for rollback

Canary

Route 10% to new version, monitor, gradually increase

Rolling

Update instances one at a time with health checks

GitHub Actions Example

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npm ci && npm run build

  test:
    needs: build
    steps:
      - run: npm test

  deploy-staging:
    needs: test
    environment: staging

  deploy-production:
    needs: deploy-staging
    environment: production

Security Practices

Never: Hardcode secrets, commit secrets, log secrets Do: Use env vars, secret management, rotate regularly

GitHub API Best Practices

Use fine-scoped PATs or GitHub Apps
Implement exponential backoff with jitter
Monitor rate limit headers
Prevent workflow cascades with concurrency

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

Best Practices

Fast feedback: CI under 10 min, parallelize
Reliable: Reproducible builds, pin versions
Visible: Clear naming, meaningful errors
Secure: Scan early, block on failures
Parity: Same config patterns across environments

End of CI/CD Pipeline Design Skill

---name: ci-cd-pipeline-designdescription: Guide developers through CI/CD pipeline design including architecture patterns, stage design, and security considerationslicense: Complete terms in LICENSE.txt--- # CI/CD Pipeline Design **Version:** 0.17.0 ## When to Use - Setting up CI/CD for new project - Optimizing pipeline performance - Adding security scanning - Designing multi-environment deployment ## CI/CD Fundamentals **CI (Integration):** Auto build/test on every change. Goal: Fast feedback (<10 min) **CD (Delivery):** Auto prepare releases. Goal: Always deployable main **CD (Deployment):** Auto deploy to production. Requires: High coverage, feature flags, monitoring ## Pipeline Architectures ### Linear ``` Build → Test → Security → Deploy ``` Best for: Simple projects ### Parallel ``` Build → [Unit|Lint|SAST] → Deploy ``` Best for: Faster feedback ### Multi-Environment ``` Build → Test → Staging → Approval → Production ``` Best for: Production deployments ## Stage Design ### Build - Cache dependencies, multi-stage builds, version artifacts ### Test (Pyramid) ``` Few E2E (slow) → Some Integration → Many Unit (fast) ``` ### Security | Type | Tools | |------|-------| | SAST | SonarQube, Semgrep, CodeQL | | Dependencies | Snyk, Dependabot | | Secrets | GitLeaks, TruffleHog | | Containers | Trivy, Clair | ### Deploy - Staging: automatic - Production: manual approval, canary rollout ## Deployment Strategies ### Blue-Green Deploy to inactive (Green), switch traffic, keep Blue for rollback ### Canary Route 10% to new version, monitor, gradually increase ### Rolling Update instances one at a time with health checks ## GitHub Actions Example ```yaml jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - run: npm ci && npm run build test: needs: build steps: - run: npm test deploy-staging: needs: test environment: staging deploy-production: needs: deploy-staging environment: production ``` ## Security Practices **Never:** Hardcode secrets, commit secrets, log secrets **Do:** Use env vars, secret management, rotate regularly ## GitHub API Best Practices - Use fine-scoped PATs or GitHub Apps - Implement exponential backoff with jitter - Monitor rate limit headers - Prevent workflow cascades with `concurrency` ```yaml concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true ``` ## Best Practices 1. **Fast feedback:** CI under 10 min, parallelize 2. **Reliable:** Reproducible builds, pin versions 3. **Visible:** Clear naming, meaningful errors 4. **Secure:** Scan early, block on failures 5. **Parity:** Same config patterns across environments --- **End of CI/CD Pipeline Design Skill**

Frequently asked questions