Verified:GitHub

ci-cd-pipelines

Name: ci-cd-pipelines
Availability: InStock
Author: timequity

Automate CI/CD pipeline design and deployment workflows for GitHub Actions and GitLab CI.

6|Updated Dec 7, 2025

Search Tags:#devops #github-actions #pipelines #ci #cd

Ready to run

npx skills add https://github.com/timequity/plugins --skill ci-cd-pipelines-timequity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-cd-pipelines
Source: https://github.com/timequity/plugins/tree/main/craft-coder/infra/ci-cd-pipelines
Command: npx skills add https://github.com/timequity/plugins --skill ci-cd-pipelines-timequity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a blueprint for building reliable CI/CD pipelines with automation and safe deployment strategies.

Core Features & Use Cases

GitHub Actions workflow templates with caching and parallel steps
Pipeline stages: Commit → Build → Test → Security → Deploy → Smoke Test
Secrets management and deployment strategies (Rolling, Blue-Green, Canary)

Quick Start

Copy the GitHub Actions template and wire up your repository.

Frequently Asked Questions about ci-cd-pipelines

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

FAQPage Schema

How do I set up a CI/CD pipeline with GitHub Actions?▼

CI/CD pipelines with GitHub Actions automate build, test, security, and deployment stages triggered by code commits. Create a workflow file in `.github/workflows/`, define stages from commit through smoke testing, configure secrets management, and GitHub Actions executes the pipeline on repository events.

What deployment strategies does a GitHub Actions pipeline support?▼

GitHub Actions pipelines support Rolling, Blue-Green, Canary, and Recreate deployment strategies. Each strategy manages how application updates are released to production environments, with trade-offs in speed, safety, and rollback capability depending on your infrastructure and risk tolerance.

Can I use GitHub Actions for both build and deployment workflows?▼

Yes, GitHub Actions handles the complete workflow from build through deployment. A single pipeline orchestrates compilation, running tests, security checks, artifact management, secret injection, and multi-stage deployments to Kubernetes or other environments with rollback support.

How do I manage secrets and artifacts in a CI/CD pipeline?▼

CI/CD pipelines manage secrets through encrypted environment variables stored in GitHub and referenced in workflow steps. Artifacts are tagged, cached, and made immutable to ensure consistency across pipeline stages and enable efficient reuse during builds and deployments.

Why use caching and parallel steps in GitHub Actions workflows?▼

Caching and parallel steps optimize pipeline speed and feedback cycles. Caching reuses dependencies and build outputs across runs, while parallel execution runs independent jobs simultaneously, reducing total execution time and supporting fail-fast checks for faster development iteration.

Does a CI/CD pipeline support Kubernetes deployments?▼

Yes, CI/CD pipelines configured with GitHub Actions support Kubernetes deployments. The pipeline can push immutable container artifacts and apply deployment manifests to Kubernetes clusters, enabling environment parity and supporting multiple deployment strategies across staging and production environments.