ci-cd

Design CI/CD pipelines for GitHub Actions, GitLab CI, and CircleCI.

110|14|Updated May 12, 2026

Search Tags:#ci/cd #github actions #deployment strategies #gitlab ci #oidc #circleci #docker cache

One-click install

npx skills add https://github.com/EliasOulkadi/shokunin --skill ci-cd-eliasoulkadi

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ci-cd
Source: https://github.com/EliasOulkadi/shokunin/tree/main/.pack/skills/ci-cd
Command: npx skills add https://github.com/EliasOulkadi/shokunin --skill ci-cd-eliasoulkadi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

It eliminates slow, fragile, and insecure release workflows by guiding you to build CI/CD pipelines that validate changes, optimize build performance, and deploy safely with strong controls.

Core Features & Use Cases

Fast, reliable pipelines: Lint, typecheck, and tests run with matrix builds and test sharding to reduce total feedback time.
Secure deployments: Uses OIDC to avoid long-lived secrets and adds environment protection with manual approvals for production.
Efficient delivery: Implements dependency caching, Docker layer caching, and clear deployment strategies (rolling, blue-green, canary), including healthcheck verification and rollback guidance.
Use case: For a GitHub-hosted service, configure build/test/deploy so every PR runs sharded tests, images are built with BuildKit caching, and production deploys require approval plus post-deploy health checks.

Quick Start

Use the ci-cd skill to design your GitHub Actions workflow by asking: "Set up a production-ready CI/CD pipeline for my Node.js app on GitHub Actions with test sharding, Docker layer caching, OIDC-based deployment, staging-to-production approvals, and automatic rollback on failed health checks."

Frequently Asked Questions about ci-cd

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

FAQPage Schema

How do I set up a production-ready CI/CD pipeline with GitHub Actions and OIDC?▼

To set up a production-ready CI/CD pipeline with GitHub Actions and OIDC, configure build, test, and deploy stages using OIDC for keyless authentication. Add environment protection with manual approvals and post-deploy health checks to ensure safe, deterministic releases without static credentials.

How does Docker layer caching improve build speed in GitLab CI?▼

Docker layer caching improves build speed in GitLab CI by storing and reusing previously built image layers. This approach, combined with dependency caching keyed to lockfiles, reduces total feedback time by avoiding redundant rebuilds across pipeline runs.

What is the best way to shard tests across a CI/CD pipeline matrix?▼

The best way to shard tests in a CI/CD pipeline is using matrix builds to split test suites across parallel runners. Test sharding significantly reduces total feedback time by executing lint, typecheck, and test stages concurrently rather than sequentially.

Can I use blue-green deployment strategies with CircleCI?▼

Yes, you can use blue-green deployment strategies with CircleCI. This approach includes rolling and canary deployments, applying healthcheck-based verification to confirm new environment stability before completing traffic shifts and rolling back failed releases.

How do I automate rollback on failed health checks during deployment?▼

Automate rollback on failed health checks by implementing deployment strategies with healthcheck-based verification in your pipeline. This ensures that if post-deploy health checks fail, the system automatically reverts to the previous stable environment without manual intervention.

Why should I use OIDC authentication instead of static credentials for deployments?▼

Use OIDC authentication instead of static credentials to avoid long-lived secrets in your CI/CD pipelines. OIDC provides secure, temporary tokens for environment protection, reducing the risk of credential leakage while maintaining guarded production releases.