ci-cd

Automate CI/CD quality gates and deployment rollback strategies for code changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Pyl-Tech/stream-coding --skill ci-cd-pyl-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd
Source: https://github.com/Pyl-Tech/stream-coding/tree/main/.agents/skills/ci-cd
Command: npx skills add https://github.com/Pyl-Tech/stream-coding --skill ci-cd-pyl-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of changes reaching production without consistent, repeatable validation by automating CI/CD quality gates that mirror the methodology’s Verify stage.

Core Features & Use Cases

  • Quality-gate CI pipeline: Enforces linting, type checking, unit tests, build, integration tests, optional E2E, security auditing, and (for frontend) bundle size checks so merges cannot occur without passing verification.
  • Deployment strategy automation: Implements preview deployments, staging, production promotion, and rollback-safe release flows (including monitoring thresholds and rollback paths).
  • Actionable CI failure feedback: Helps feed failure outputs back to agents for targeted debugging and iterative reruns rather than ad-hoc retries.

Use Case Example: When adding a new backend service, configure GitHub Actions to run lint/type/test/build plus security audits on every pull request, then deploy to Cloud Run only after staging verification and use documented rollback procedures if error or latency thresholds are breached.

Quick Start

Set up a CI workflow that runs lint, type check, unit tests, build, security audit, and blocks merge on failure for every push and pull request to main.

Frequently Asked Questions about ci-cd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up CI/CD quality gates to block unverified code from merging?

CI/CD quality gates block merges by enforcing lint, type check, unit tests, build, integration tests, and security audits on every pull request. Merges cannot occur without passing verification.

What is the best way to automate deployment and rollback strategies for GitHub Actions?

Automate deployment and rollback strategies by orchestrating preview deployments, staging verification, and production promotion. This includes monitoring error thresholds and documenting rollback paths for safe releases.

Can I use CI/CD automation to feed failure outputs back to agents for debugging?

Yes, CI/CD automation provides actionable failure feedback. It feeds failure outputs back to agents for targeted debugging and iterative reruns rather than relying on ad-hoc retries.

Does a CI/CD pipeline need bundle size and E2E checks for frontend services?

A CI/CD pipeline requires bundle size and optional E2E checks specifically for frontend services. Core quality gates like integration tests and security audits remain mandatory for all changes.

Why do I need a documented rollback strategy in my deployment pipeline?

A documented rollback strategy is needed in your deployment pipeline to safely revert production changes. It triggers when error or latency thresholds are breached after a deployment promotion.

How to handle secure secrets when automating CI/CD workflows?

Handle secure secrets in CI/CD workflows by enforcing secure secret handling within the pipeline configuration. This prevents unverified changes from reaching production during deployment orchestration.