ci-cd

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

37|1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/saolalab/clawforce --skill ci-cd-saolalab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd
Source: https://github.com/saolalab/clawforce/tree/main/marketplace/roles/devops-engineer/workspace/skills/ci-cd
Command: npx skills add https://github.com/saolalab/clawforce --skill ci-cd-saolalab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CI/CD pipelines are often slow, fragile, and insecure, causing delayed feedback, failed releases, and operational overhead; this Skill helps design and manage pipelines that deliver reliable, fast, and secure software delivery workflows.

Core Features & Use Cases

  • Pipeline Architecture & Best Practices: Defines stages like build, test, security scan, deploy, verify, and monitor with recommendations for reproducible builds, caching, parallel execution, and artifact versioning.
  • Testing & Quality Gates: Prioritizes fast feedback with unit-first testing, parallelized suites, flaky test handling, and coverage gates to block regressions.
  • Security & Safe Deployments: Recommends SAST, dependency and secret scanning, container image checks, environment promotion, rollout strategies (blue-green/canary), and rollback capability.
  • Use Case: Create a GitHub Actions workflow that builds and tests a Node.js app, scans dependencies and container images, uploads artifacts, and deploys to staging with a manual gate for production.

Quick Start

Use this skill to design a GitHub Actions pipeline that builds, tests, scans, and deploys your application through dev, staging, and production with safe rollback and monitoring.

Frequently Asked Questions about ci-cd

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

FAQPage Schema
How do I design a GitHub Actions pipeline for build, test, and deployment?

To design a GitHub Actions pipeline, structure stages for build, test, security scan, deploy, verify, and monitor using reproducible builds, caching, and parallel execution. This ensures fast feedback, reliable artifact versioning, and safe deployments across dev, staging, and production environments.

What is the best way to handle flaky tests and slow CI/CD pipelines?

The best way to handle flaky tests and slow pipelines is to prioritize unit-first testing, parallelize test suites, and implement coverage gates. Caching and parallel execution further optimize build time and pipeline success rate, blocking regressions while accelerating feedback.

How do I add security scanning and safe rollout strategies to my deployment pipeline?

To add security and safe rollouts, integrate SAST, dependency scanning, secret scanning, and container image checks into your pipeline. Use environment promotion with blue-green or canary rollout strategies, ensuring rollback capability for production deployments.

Can I use manual deployment gates for production in my CI/CD workflow?

Yes, you can use manual deployment gates for production. The pipeline can build, test, scan, and upload artifacts, then deploy to staging and require a manual approval gate before promoting the application to the production environment.

Why does my CI/CD pipeline need artifact versioning and environment promotion?

Your CI/CD pipeline needs artifact versioning and environment promotion to ensure reproducible builds and safe software delivery. Versioning tracks build outputs accurately, while promotion moves verified artifacts through dev, staging, and production gates securely.

What metrics should I monitor to troubleshoot failing CI/CD pipelines?

You should monitor build time and pipeline success rate metrics to troubleshoot failing pipelines. Tracking these metrics alongside parallelized testing and deployment verification helps identify slow stages, flaky tests, and operational overhead in your workflow.