ci-cd-and-automation

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

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/jampissarandev/Expense-Tracker --skill ci-cd-and-automation-jampissarandev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd-and-automation
Source: https://github.com/jampissarandev/Expense-Tracker/tree/main/.github/skills/ci-cd-and-automation
Command: npx skills add https://github.com/jampissarandev/Expense-Tracker --skill ci-cd-and-automation-jampissarandev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams shipping code without automated verification accumulate broken builds, undetected bugs, and risky deployments. This Skill establishes a consistent CI/CD pipeline so every change passes lint, type checks, tests, and builds before merge, and every deployment has a rollback path. ## Core Features & Use Cases - Quality Gate Pipelines: Defines an ordered gate sequence (lint, type check, unit tests, build, integration, E2E, security audit, bundle size) with ready-to-use GitHub Actions YAML for Node.js and PostgreSQL-backed projects. - Deployment Strategies: Covers preview deployments per PR, feature flags, staged rollouts, and manual rollback workflows so releases stay reversible. - CI Feedback Loop for Agents: Provides patterns for feeding CI failure output back to AI agents so they can fix lint, type, test, and build errors autonomously. - Use Case: A team bootstrapping a new React + Node project uses this Skill to generate a GitHub Actions workflow with parallel lint/typecheck/test jobs, Postgres service containers for integration tests, Playwright E2E, and branch protection rules. ## Quick Start Ask the agent to set up a GitHub Actions CI pipeline for the project with lint, type checking, tests, build, and a rollback workflow.

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 runs on pull requests and pushes to main. Add jobs for lint, type checking with tsc --noEmit, tests with coverage, build, and npm audit, using actions/setup-node with dependency caching.

How to run integration tests with PostgreSQL in GitHub Actions?

Define a postgres service container in the job with health checks, then pass the DATABASE_URL using GitHub Secrets for credentials. Run migrations before executing the integration test suite against the service on localhost:5432.

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 skippable, and branch protection should block merges when any gate fails.

How do I speed up a slow CI pipeline?

Cache dependencies with setup-node's cache option, split lint, typecheck, and test into parallel jobs, use path filters to skip unrelated jobs, shard test suites with matrix builds, and move slow tests off the critical path.

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

Use feature flags to merge incomplete or risky features to main without enabling them, enabling canary rollouts and instant rollback without redeploying. Set a cleanup date when creating each flag so stale flags do not become technical debt.