ci-cd-and-automation

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

Updated May 21, 2026
One-click install
npx skills add https://github.com/nicorevo/AI-SDLC-Template --skill ci-cd-and-automation-nicorevo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-cd-and-automation
Source: https://github.com/nicorevo/AI-SDLC-Template/tree/main/.opencode/skills/ci-cd-and-automation
Command: npx skills add https://github.com/nicorevo/AI-SDLC-Template --skill ci-cd-and-automation-nicorevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Without automated pipelines, broken code reaches production, quality checks are skipped under pressure, and deployments become risky manual events. This Skill enforces lint, type checking, tests, build, and security audits on every change so no unverified code is merged. ## Core Features & Use Cases - Quality Gate Pipelines: GitHub Actions workflows covering lint, type check, unit tests, build, integration tests with PostgreSQL services, E2E tests with Playwright, and security audits. - Deployment Strategies: Preview deployments per PR, feature flags, staged rollouts with monitoring windows, and manual rollback workflows. - CI Optimization & Feedback Loops: Caching, parallel jobs, path filters, and matrix builds 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 pipeline that blocks merges until lint, tests, and build pass, with Dependabot configured for dependency updates. ## Quick Start Set up a CI pipeline for my project that runs lint, type checks, tests, and build on every pull request and blocks merging when any check fails.

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 triggered on pull requests and pushes to main. Add sequential 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 CI?▼

Use GitHub Actions services to spin up a PostgreSQL 16 container with health checks, then run migrations and integration tests against it. Store the database password in GitHub Secrets rather than hardcoding credentials.

What should I do when CI tests are flaky?▼

Fix the flakiness rather than re-running or disabling the test, since flaky tests mask real bugs and waste time. Never skip a failing gate; fix the underlying code or test instead.

How do I speed up a slow CI pipeline?▼

Apply optimizations in order of impact: cache dependencies, split lint, typecheck, test, and build into parallel jobs, use path filters to skip unrelated jobs, shard tests 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, allowing canary rollouts and instant rollback by disabling the flag. Set a cleanup date when creating flags so they do not become permanent technical debt.