ci-cd-and-automation

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

Updated May 5, 2026
One-click install
npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill ci-cd-and-automation-nikegeorgian-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-cd-and-automation
Source: https://github.com/nikegeorgian-stack/otgruzka-tovara/tree/main/.cursor/skills/ci-cd-and-automation
Command: npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill ci-cd-and-automation-nikegeorgian-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Broken code reaches production when teams rely on manual checks or skip verification. This Skill establishes automated quality gates so every change passes lint, type checks, tests, build, and security audits before merge. ## Core Features & Use Cases - Quality Gate Pipelines: GitHub Actions workflows covering lint, TypeScript type checking, unit tests, build, integration tests with PostgreSQL services, E2E tests with Playwright, and npm security audits. - Deployment Strategies: Preview deployments per pull request, feature flags, staged rollouts to staging and production, and manual rollback workflows via Vercel. - CI Optimization & Feedback Loops: Dependency caching, parallel jobs, path filters, and patterns for feeding CI failure output back to AI agents for automated fixes. - Use Case: A team setting up a new Node.js project uses this Skill to create a GitHub Actions pipeline that blocks merges until lint, tests, and build pass, with preview deployments on every PR. ## Quick Start Set up a GitHub Actions CI pipeline for my Node.js project with lint, type check, tests, build, and branch protection on main.

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 jobs for lint, TypeScript type checking with tsc --noEmit, tests, build, and npm audit, using actions/setup-node with npm caching.

How to run integration tests with a database in GitHub Actions?▼

Define a postgres service container in the workflow job with health checks, then run migrations and integration tests against it using a DATABASE_URL environment variable. Store credentials in GitHub Secrets rather than hardcoding them.

What is the difference between feature flags and staged rollouts?▼

Feature flags decouple deployment from release by toggling features in code at runtime, enabling canary releases and instant disable. Staged rollouts promote builds through staging to production environments with verification between stages.

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

Slow pipelines usually lack dependency caching and run jobs sequentially. Enable the setup-node npm cache, 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 credentials stored in GitHub Secrets for CI testing, and keep production secrets in the deployment platform or a vault.