ci-cd-and-automation

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

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/JacobThree/zero-bloat-mcp-stack --skill ci-cd-and-automation-jacobthree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-cd-and-automation
Source: https://github.com/JacobThree/zero-bloat-mcp-stack/tree/main/ai_blueprints/agent-skills/skills/ci-cd-and-automation
Command: npx skills add https://github.com/JacobThree/zero-bloat-mcp-stack --skill ci-cd-and-automation-jacobthree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents broken code from reaching production by enforcing automated quality gates—lint, type checks, tests, builds, and security audits—on every pull request, replacing inconsistent manual verification. ## Core Features & Use Cases - Quality Gate Pipelines: Defines a staged pipeline (lint, typecheck, unit tests, build, integration, E2E, security audit, bundle size) with ready-to-use GitHub Actions YAML configurations. - Deployment Strategies: Covers preview deployments, feature flags, staged rollouts, and manual rollback workflows so every deployment is reversible. - CI Optimization & Feedback Loops: Provides caching, parallelism, and path-filter strategies to keep pipelines under 10 minutes, plus patterns for feeding CI failures back to AI agents for automated fixes. - Use Case: When setting up a new Node.js project, use this Skill to generate a complete GitHub Actions workflow with Postgres integration tests, Playwright E2E runs, and branch protection rules. ## Quick Start Set up a GitHub Actions CI pipeline for my project with lint, type checking, tests, build, and a security audit that blocks merging on failure.

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 CI pipeline with GitHub Actions?▼

Create a workflow file at .github/workflows/ci.yml that triggers on pull requests and pushes to main. Add sequential steps for npm ci, lint, tsc --noEmit, tests with coverage, build, and npm audit, using actions/setup-node with dependency caching.

How to run integration tests with Postgres in GitHub Actions?▼

Define a postgres service container in the job with health checks, expose port 5432, and store credentials in GitHub Secrets. Run migrations with prisma migrate deploy, then execute integration tests against the service using the DATABASE_URL environment variable.

Why is my CI pipeline slow and how do I speed it up?▼

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 matrix runners.

Should I skip CI for small or trivial changes?▼

No, trivial changes frequently break builds and CI runs quickly for small diffs anyway. The skill treats every gate as mandatory—fix lint errors rather than disabling rules, and fix failing tests rather than skipping them.

How do feature flags work with continuous deployment?▼

Feature flags decouple deployment from release by gating new code behind runtime checks, enabling canary rollouts and instant rollback without redeploying. Flags should follow a lifecycle from creation through full rollout to removal, since permanent flags become technical debt.

What should I do when CI fails on my pull request?▼

Copy the specific failure output and feed it to your AI agent with instructions to fix and verify locally before pushing. Lint failures map to npm run lint --fix, type errors to the reported location, and test failures to a debugging workflow.