ci-cd-pipeline

Design GitHub Actions CI/CD pipelines for build, test, and secure deployment.

364|53|Updated May 9, 2026
One-click install
npx skills add https://github.com/cosmicstack-labs/mercury-agent-skills --skill ci-cd-pipeline-cosmicstack-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd-pipeline
Source: https://github.com/cosmicstack-labs/mercury-agent-skills/tree/main/categories/devops/ci-cd-pipeline
Command: npx skills add https://github.com/cosmicstack-labs/mercury-agent-skills --skill ci-cd-pipeline-cosmicstack-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you stop fragile, slow, and insecure release processes by giving a practical blueprint for production-grade CI/CD pipelines.

Core Features & Use Cases

  • Workflow design for speed and reliability: Lint, type check, unit, integration, and e2e testing staged for fast feedback and fail-fast behavior.
  • Secure deployments and environment management: Uses GitHub Environments, secret hygiene, OIDC-based auth, and least-privilege patterns.
  • Production-safe delivery patterns: Build once and promote immutable artifacts, add concurrency controls, and support rollback and pipeline security gates (e.g., SBOM/vuln scanning).

Use case: You maintain a web service in a monorepo and need GitHub Actions that runs targeted tests only for changed parts, builds once, deploys to staging, then requires approval before deploying the exact same artifact to production.

Quick Start

Ask an AI to produce a GitHub Actions CI/CD pipeline that runs lint and unit tests quickly, shards integration/e2e checks, builds once into a single immutable artifact, deploys to staging automatically, and deploys to production only after an environment approval gate with secure (OIDC) authentication and pinned action versions.

Frequently Asked Questions about ci-cd-pipeline

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

FAQPage Schema
How do I design a secure CI/CD pipeline in GitHub Actions from commit to production?

To design a secure CI/CD pipeline, structure GitHub Actions workflows to automate build, test, and secure deployment using fail-fast testing gates, immutable artifact promotion, and OIDC-based authentication for multi-environment delivery.

What's the best way to manage secrets and deployments across multiple environments in GitHub Actions?

Managing secrets and deployments across multiple environments requires using GitHub Environments with least-privilege patterns, strict secret hygiene, and OIDC-based auth to ensure secure, environment-specific access controls.

How do I configure monorepo-aware triggers to run targeted tests only for changed parts?

Configuring monorepo-aware triggers involves setting up GitHub Actions workflows with path filters and concurrency controls, ensuring that only tests relevant to the changed code paths execute for faster feedback.

How does build once and promote immutable artifacts work in a CI/CD pipeline?

Build once and promote immutable artifacts means compiling a single artifact in the initial CI stage, then deploying that exact unmodified artifact through staging to production, ensuring reproducibility and preventing environment drift.

Can I add supply-chain security gates like vulnerability and SBOM scanning to GitHub Actions?

You can add supply-chain security gates by integrating vulnerability scanning and SBOM generation into your GitHub Actions workflows, alongside pinning action versions to secure the CI/CD pipeline against external tampering.

How do I set up an environment approval gate before deploying to production in GitHub Actions?

Setting up an environment approval gate requires configuring GitHub Environments to require manual approval, ensuring the CI/CD pipeline pauses for authorization before promoting the immutable artifact to production.