ci-cd

Automate GitHub Actions CI/CD pipelines for TypeScript/Node repositories.

4|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/rbaumier/skills --skill ci-cd-rbaumier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd
Source: https://github.com/rbaumier/skills/tree/main/ci-cd
Command: npx skills add https://github.com/rbaumier/skills --skill ci-cd-rbaumier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enforces reliable CI/CD pipelines so pull requests are validated, builds are reproducible, tests run in the correct order, secrets are protected, and deployments are reversible.

Core Features & Use Cases

  • Quality Gates: Enforces ordered gates (lint → type-check → unit tests → build → integration → E2E → security audit → bundle size) and recommends running the first gates in parallel.
  • GitHub Actions Best Practices: Provides job splitting, pinned actions, dependency caching, artifact caching, concurrency controls, and Playwright setup for E2E.
  • Integration & E2E Testing: Shows how to run integration tests with service containers (Postgres) and E2E with Playwright including failure artifact uploads.
  • Monorepo & Path Filtering: Uses path filters or dorny/paths-filter to run only affected jobs in monorepos.
  • Deployment & Rollback Strategies: Recommends rolling/canary/blue-green strategies, staged rollouts with verification thresholds, and a dedicated rollback workflow.
  • Security & Environment Management: Stresses GitHub Secrets, environment separation, and branch protection rules to block merges on failing checks.

Quick Start

Set up the GitHub Actions workflow with parallel lint/typecheck/test jobs, a dependent build job, conditional integration and E2E jobs, dependency and artifact caching, secure secrets via GitHub Secrets, and a rollback workflow.

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 GitHub Actions quality gates for a Node.js monorepo?

GitHub Actions quality gates enforce ordered lint, type-check, unit test, build, integration, E2E, security audit, and bundle size checks. Running initial gates in parallel with dependency caching ensures fast, reliable pull request validation.

How do I run Playwright E2E tests with GitHub Actions service containers?

Running Playwright E2E tests in GitHub Actions requires configuring service containers for database integration and setting up artifact uploads for failure logs. This ensures browser tests validate application changes against a realistic environment.

Can I use path filtering to skip unaffected jobs in a monorepo CI/CD pipeline?

Yes, path filtering skips unaffected jobs in a monorepo CI/CD pipeline using dorny/paths-filter. This targets specific changed directories, running only necessary build and test jobs to optimize GitHub Actions resource usage.

What is the best way to configure staged deployments and rollbacks in GitHub Actions?

Configuring staged deployments and rollbacks in GitHub Actions involves rolling, canary, or blue-green strategies with verification thresholds. A dedicated rollback workflow ensures changes are reversible if production verification fails.

How do GitHub Secrets and branch protection secure CI/CD pipelines?

GitHub Secrets secure CI/CD pipelines by encrypting sensitive deployment credentials, while branch protection rules block merges when checks fail. This enforces environment separation and prevents unauthorized or broken deployments.