Cicd Pipeline Setup

aj-geddes/useful-ai-prompts/skills/cicd-pipeline-setup

by aj-geddes3f5182cfd739No license355 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 7 months ago

Design and implement CI/CD pipelines with GitHub Actions, GitLab CI, Jenkins, or CircleCI. Use for automated testing, building, and deployment workflows.

Includes scriptsDevOps & Cloud
AI-generated overview

Designs and implements CI/CD pipelines for GitHub Actions, GitLab CI, Jenkins, or CircleCI.

What it does
This skill helps build automated continuous integration and deployment pipelines that test code, build artifacts, run security checks, and deploy to multiple environments. It provides reference guides for GitHub Actions, GitLab CI, Jenkins, and CI/CD scripting, plus a pipeline template and a validation script. It produces pipeline configuration and workflow definitions for automated testing, building, and deployment.
When to use it
Use it when setting up automated code testing and quality checks, containerized application builds, multi-environment deployments, release management, or automated security and performance testing. It is meant for teams that want to reduce manual intervention in build and deployment workflows.
Requirements
Ships executable scripts, including scripts/validate-pipeline.sh, and a pipeline template. It targets CI/CD platforms such as GitHub Actions, GitLab CI, Jenkins, or CircleCI, which require access to the relevant repository and platform credentials for deployment.

CI/CD Pipeline Setup

Table of Contents

Overview

Build automated continuous integration and deployment pipelines that test code, build artifacts, run security checks, and deploy to multiple environments with minimal manual intervention.

When to Use

  • Automated code testing and quality checks
  • Containerized application builds
  • Multi-environment deployments
  • Release management and versioning
  • Automated security scanning
  • Performance testing integration
  • Artifact management and registry

Quick Start

Minimal working example:

yaml
# .github/workflows/deploy.ymlname: Build and Deploy
on:  push:    branches:      - main      - develop  pull_request:    branches:      - main  workflow_dispatch:
env:  REGISTRY: ghcr.io  IMAGE_NAME: ${{ github.repository }}
jobs:  test:    runs-on: ubuntu-latest    strategy:      matrix:        node-version: [18.x, 20.x]
    steps:// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
GitHub Actions Workflow [blocked]GitHub Actions Workflow
GitLab CI Pipeline [blocked]GitLab CI Pipeline
Jenkins Pipeline [blocked]Jenkins Pipeline
CI/CD Script [blocked]CI/CD Script

Best Practices

✅ DO

  • Fail fast with early validation
  • Run tests in parallel when possible
  • Use caching for dependencies
  • Implement proper secret management
  • Gate production deployments with approval
  • Monitor and alert on pipeline failures
  • Use consistent environment configuration
  • Implement infrastructure as code

❌ DON'T

  • Store credentials in pipeline configuration
  • Deploy without automated tests
  • Skip security scanning
  • Allow long-running pipelines
  • Mix staging and production pipelines
  • Ignore test failures
  • Deploy directly to main branch
  • Skip health checks after deployment

Source and attribution

Source:aj-geddes/useful-ai-promptsinskills/cicd-pipeline-setupat commit3f5182c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Cicd Pipeline Setup · skills/cicd-pipeline-setup Agent Skill | SourceWeft