Back to skills
SkillHub ClubRun DevOpsDevOpsTesting

ci-cd-pipelines

Provides CI/CD pipeline templates for GitHub Actions with clear examples for test, build, and deploy stages. Includes Docker container building, deployment strategies comparison, and best practices like immutable artifacts and secrets management.

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars
5
Hot score
82
Updated
March 20, 2026
Overall rating
A7.8
Composite score
5.0
Best-practice grade
B81.2

Install command

npx @skill-hub/cli install timequity-plugins-ci-cd-pipelines
github-actionsci-cddeploymentdocker

Repository

timequity/plugins

Skill path: craft-coder/infra/ci-cd-pipelines

Provides CI/CD pipeline templates for GitHub Actions with clear examples for test, build, and deploy stages. Includes Docker container building, deployment strategies comparison, and best practices like immutable artifacts and secrets management.

Open repository

Best for

Primary workflow: Run DevOps.

Technical facets: DevOps, Testing.

Target audience: Developers and DevOps engineers setting up new CI/CD pipelines, particularly those using GitHub Actions and Docker containers.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: timequity.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

  • Install ci-cd-pipelines into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
  • Review https://github.com/timequity/plugins before adding ci-cd-pipelines to shared team environments
  • Use ci-cd-pipelines for devops workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: ci-cd-pipelines
description: CI/CD pipeline design with GitHub Actions, GitLab CI, and best practices.
---

# CI/CD Pipelines

## GitHub Actions

```yaml
name: CI/CD

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm test

  build:
    needs: test
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: docker/setup-buildx-action@v3
      - uses: docker/login-action@v3
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}
      - uses: docker/build-push-action@v5
        with:
          push: true
          tags: ghcr.io/${{ github.repository }}:${{ github.sha }}

  deploy:
    needs: build
    if: github.ref == 'refs/heads/main'
    runs-on: ubuntu-latest
    environment: production
    steps:
      - name: Deploy to Kubernetes
        run: |
          kubectl set image deployment/app \
            app=ghcr.io/${{ github.repository }}:${{ github.sha }}
```

## Pipeline Stages

```
Commit → Build → Test → Security → Deploy → Smoke Test
           │       │       │
           └───────┴───────┴── Parallel
```

## Best Practices

- **Fast feedback** - Tests < 10 min
- **Fail fast** - Critical checks first
- **Cache dependencies** - Avoid re-downloading
- **Immutable artifacts** - Tag with commit SHA
- **Environment parity** - Same image everywhere
- **Rollback ready** - Quick revert capability

## Secrets Management

```yaml
# GitHub Actions
env:
  DATABASE_URL: ${{ secrets.DATABASE_URL }}

# With OIDC (no secrets)
- uses: aws-actions/configure-aws-credentials@v4
  with:
    role-to-assume: arn:aws:iam::123456789:role/github-actions
    aws-region: us-east-1
```

## Deployment Strategies

| Strategy | Risk | Rollback |
|----------|------|----------|
| **Rolling** | Low | Slow |
| **Blue-Green** | Low | Fast |
| **Canary** | Very Low | Fast |
| **Recreate** | High | Fast |
ci-cd-pipelines | SkillHub