ci-cd-and-automation

Configures GitHub Actions CI/CD pipelines with quality gates, deployment strategies, and rollback workflows.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/raishoemi/traffic-sim-v2 --skill ci-cd-and-automation-raishoemi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd-and-automation
Source: https://github.com/raishoemi/traffic-sim-v2/tree/main/.github/skills/ci-cd-and-automation
Command: npx skills add https://github.com/raishoemi/traffic-sim-v2 --skill ci-cd-and-automation-raishoemi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up reliable CI/CD pipelines is error-prone: teams skip quality gates, hardcode secrets, deploy without rollback plans, and let slow pipelines erode trust in automation. This Skill provides a complete, opinionated framework for building pipelines that enforce lint, type checks, tests, builds, and security audits on every change. ## Core Features & Use Cases - Quality Gate Pipelines: Ready-to-use GitHub Actions workflows covering lint, type checking, unit tests, builds, integration tests with PostgreSQL services, E2E tests with Playwright, and security audits. - Deployment Strategies: Guidance for preview deployments, feature flags, staged rollouts, and manual rollback workflows so every deployment is reversible. - CI Optimization & Feedback Loops: Strategies for caching, parallel jobs, and path filters to keep pipelines under 10 minutes, plus patterns for feeding CI failures back to AI agents for automated fixes. - Use Case: You are scaffolding a new React + Vite project and need branch protection, automated checks on every PR, and a staging-to-production deployment flow. This Skill gives you the exact YAML configurations and verification checklist to set it up correctly on day one. ## Quick Start Ask the agent to set up a GitHub Actions CI pipeline for this repository with lint, type check, tests, build, and a security audit as required status checks.

Frequently Asked Questions about ci-cd-and-automation

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

FAQPage Schema
How do I set up a GitHub Actions CI pipeline for a Node.js project?

Create a workflow triggered on pull requests and pushes to main that runs npm ci, lint, tsc --noEmit, tests with coverage, build, and npm audit. Use actions/setup-node with the cache option to speed up dependency installation.

How to run integration tests with PostgreSQL in GitHub Actions?

Define a postgres service container in the workflow job with health checks, then run migrations and tests against localhost:5432. Store the CI database password in GitHub Secrets rather than hardcoding it in the workflow file.

What quality gates should a CI pipeline include?

A complete pipeline includes lint, type checking, unit tests, build, integration tests, optional E2E tests, security audit, and bundle size checks. No gate should be skipped, and failures should block merging through branch protection rules.

Why is my CI pipeline slow and how do I fix it?

Slow pipelines usually lack dependency caching and run jobs sequentially. Apply caching via setup-node, split lint, typecheck, and test into parallel jobs, use path filters to skip unrelated work, and shard large test suites across runners.

Should CI pipelines have access to production secrets?

No, CI should never hold production secrets. Use separate secrets for CI testing stored in GitHub Secrets, keep production credentials in the deployment platform or a vault, and commit only template files like .env.example.

How do feature flags work with continuous deployment?

Feature flags decouple deployment from release by gating new code behind runtime checks. Deploy incomplete features to main safely, enable them gradually for canary users, and remove the flag and dead code after full rollout.