ci-cd-and-automation

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

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill ci-cd-and-automation-kunj-sharma03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd-and-automation
Source: https://github.com/Kunj-Sharma03/agent-contextify/tree/main/templates/skills/ci-cd-and-automation
Command: npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill ci-cd-and-automation-kunj-sharma03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up reliable CI/CD pipelines is error-prone and often postponed, leaving projects without automated quality gates. This Skill provides ready-to-use pipeline configurations and deployment strategies so every change is verified by lint, type checks, tests, and builds before reaching production. ## Core Features & Use Cases - Quality Gate Pipelines: Enforce lint, type checking, unit tests, build, integration tests, security audits, and bundle size checks on every pull request. - GitHub Actions Templates: Copy-ready workflow YAML for basic CI, database-backed integration tests with Postgres services, and Playwright E2E tests. - Deployment Strategies: Implement preview deployments, feature flags, staged rollouts, and rollback workflows with environment and secrets management. - Use Case: When starting a new Node.js project, use this Skill to scaffold a complete GitHub Actions CI pipeline that blocks merges until all quality gates pass, then add a staging-to-production deployment flow with a manual rollback option. ## Quick Start Ask the agent to set up a GitHub Actions CI pipeline for your project with lint, type check, tests, and build 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 runs on pull requests and pushes to main. Include steps for checkout, Node setup with npm caching, dependency install, lint, type check, tests, build, and a security audit.

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 quality gates should a CI pipeline include?

A complete pipeline runs lint, type checking, unit tests, build, integration tests, optional E2E tests, security audit, and bundle size checks. No gate should be skipped, and 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 for node_modules, 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 merge incomplete or risky features to main without enabling them for users. They allow canary rollouts, A/B tests, and instant rollback by disabling the flag, but flags should be removed after full rollout to avoid technical debt.