ci-cd-and-automation

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

3|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/marcmarti9/agentit --skill ci-cd-and-automation-marcmarti9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-cd-and-automation
Source: https://github.com/marcmarti9/agentit/tree/main/skills/ci-cd-and-automation
Command: npx skills add https://github.com/marcmarti9/agentit --skill ci-cd-and-automation-marcmarti9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams shipping code without automated verification accumulate broken builds, undetected bugs, and risky deployments. This Skill provides a complete operating guide for setting up CI/CD pipelines that enforce lint, type checking, tests, builds, and security audits on every change before merge. ## Core Features & Use Cases - Quality Gate Pipelines: Defines a staged pipeline covering lint, type check, unit tests, build, integration tests, E2E tests, security audit, and bundle size checks, with ready-to-use GitHub Actions YAML configurations including Postgres service containers and Playwright E2E jobs. - Deployment Strategies: Covers preview deployments per PR, feature flags with lifecycle management, staged rollouts with monitoring windows, and manual rollback workflows. - CI Optimization and Feedback Loops: Provides caching, parallelism, path filtering, and test sharding strategies to keep pipelines under 10 minutes, plus patterns for feeding CI failure output back to AI agents for automated fixes. - Use Case: When starting a new TypeScript project, use this Skill to generate a GitHub Actions workflow that runs lint, tsc --noEmit, Jest tests, and npm audit on every pull request, with branch protection blocking merges on failure. ## Quick Start Set up a GitHub Actions CI pipeline for my Node.js project with lint, type check, tests, build, and security audit gates that block 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. Use actions/checkout and actions/setup-node with npm caching, then run lint, tsc --noEmit, tests with coverage, build, and npm audit as sequential steps.

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

Define a postgres service container in the job with health checks using pg_isready, then run migrations and integration tests with a DATABASE_URL pointing at localhost:5432. Store the CI database password in GitHub Secrets rather than hardcoding it.

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; failures must 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 test suites across runners.

When should I use feature flags instead of long-lived branches?▼

Use feature flags to decouple deployment from release when shipping incomplete or risky features. Flags enable canary rollouts, instant rollback without redeploying, and A/B tests, but each flag needs a cleanup date to avoid technical debt.

Can CI pipelines use production secrets for testing?▼

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