agentleFS
mikulgohilmikulgohil/claude-skills/skills/devex/ci-cd/SKILL.md

ci-cd

Skill0 starsChanged 5 months agoMITView on GitHub

CI/CD pipeline patterns with GitHub Actions — build/test/deploy workflows, caching, matrix builds, release automation, and testing strategies. Use when writing or improving a pipeline.

  • Reads credentials
  • Commits and pushes

38 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use caching, api-versioning and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • wpankSkill

    caching

    Caching strategies, invalidation, eviction policies, HTTP caching, distributed caching, and anti-patterns. Use when designing cache layers, choosing eviction policies, debugging stale data, or optimizing read-heavy workloads.

    Also in 5 projects that use this

  • wpankSkill

    api-versioning

    API versioning strategies — URL path, header, query param, content negotiation — with breaking change classification, deprecation timelines, migration patterns, and multi-version support. Use when evolving APIs, planning breaking changes, or managing version lifecycles.

    Also in 3 projects that use this

  • SentrySkill

    feature-flags

    Gate a Sentry feature behind a FlagPole feature flag. Use when adding a feature flag, registering a flag in temporary.py, checking a flag from Python or the frontend, enabling a flag in tests, or asking where FlagPole rollout config lives. Trigger on "add a feature flag", "gate this behind a flag", "register a flag", "features.has", "api_expose", "OrganizationFeature", "ProjectFeature", "FlagPole".

    Also in 4 projects that use this

  • OpenAISkill

    auth

    Authentication integration guidance — Clerk (native Vercel Marketplace), Descope, and Auth0 setup for Next.js applications. Covers middleware auth patterns, sign-in/sign-up flows, and Marketplace provisioning. Use when implementing user authentication.

    Also in 4 projects that use this

  • wrsmith108Skill

    docker

    Container-based development for isolated, reproducible environments. Use when running npm commands, installing packages, executing code, or managing project dependencies. Trigger phrases include "npm install", "run the build", "start the server", "install package", or any code execution request.

    Also in 9 projects that use this

  • OpenAISkill

    observability

    Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

    Also in 13 projects that use this

The file

Files
SKILL.md

CI/CD Operations

Comprehensive patterns for continuous integration, delivery, and deployment using GitHub Actions, release automation tools, and testing pipelines.

GitHub Actions Quick Reference

Workflow File Anatomy

name: CI                          # Display name in Actions tab
on:                               # Trigger events
  push:
    branches: [main]
  pull_request:
    branches: [main]

permissions:                      # GITHUB_TOKEN scope (least privilege)
  contents: read
  pull-requests: write

concurrency:                      # Prevent duplicate runs
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

env:                              # Workflow-level environment variables
  NODE_VERSION: "20"

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: ${{ env.NODE_VERSION }}
          cache: npm
      - run: npm ci
      - run: npm test

Core Syntax Elements

ElementPurposeExample
onEvent triggerspush, pull_request, schedule
jobs.<id>.runs-onRunner selectionubuntu-latest, self-hosted
jobs.<id>.needsJob dependenciesneeds: [build, lint]
jobs.<id>.ifConditional executionif: github.event_name == 'push'
jobs.<id>.strategy.matrixParallel variantsnode-version: [18, 20, 22]
jobs.<id>.environmentDeployment targetenvironment: production
jobs.<id>.permissionsToken scopecontents: write
steps[*].usesUse an actionuses: actions/checkout@v4
steps[*].runRun a commandrun: npm test
steps[*].envStep environmentenv: { CI: true }

Trigger Decision Tree

ScenarioTriggerConfig
Run tests on every PRpull_requestbranches: [main]
Deploy on merge to mainpushbranches: [main]
Release on version tagpushtags: ['v*']
Nightly buildsschedulecron: '0 2 * * *'
Manual deploymentworkflow_dispatchinputs: { environment: ... }
Called by another workflowworkflow_callinputs:, secrets:
On PR label changepull_requesttypes: [labeled]
On issue commentissue_commenttypes: [created]
On release publishedreleasetypes: [published]
On package pushregistry_packagetypes: [published]

Trigger Filter Patterns

on:
  push:
    branches: [main, 'release/**']      # Branch patterns
    paths: ['src/**', '!src/**/*.test.*'] # Path filters (ignore tests)
    tags: ['v*']                          # Tag patterns
  pull_request:
    types: [opened, synchronize, reopened] # Default types
    paths-ignore: ['docs/**', '*.md']     # Ignore docs-only changes

Caching Strategies

EcosystemAction / KeyPathRestore Key
Node (npm)actions/setup-node with cache: npmAutoAuto
Node (pnpm)actions/setup-node with cache: pnpmAutoAuto
Go modulesactions/setup-go with cache: trueAutoAuto
Cargoactions/cache@v4~/.cargo/registry, targetcargo-${{ runner.os }}-${{ hashFiles('Cargo.lock') }}
pip / uvactions/setup-python with cache: pipAutoAuto
Docker layersdocker/build-push-actionUses buildx cachetype=gha or type=registry
Gradleactions/setup-java with cache: gradleAutoAuto
Composeractions/cache@v4vendorcomposer-${{ hashFiles('composer.lock') }}

Manual Cache Example

- uses: actions/cache@v4
  with:
    path: |
      ~/.cargo/bin
      ~/.cargo/registry
      ~/.cargo/git
      target
    key: cargo-${{ runner.os }}-${{ hashFiles('**/Cargo.lock') }}
    restore-keys: |
      cargo-${{ runner.os }}-

Matrix Strategy

strategy:
  fail-fast: false                    # Don't cancel siblings on failure
  max-parallel: 4                     # Limit concurrent jobs
  matrix:
    os: [ubuntu-latest, windows-latest, macos-latest]
    node-version: [18, 20, 22]
    include:                          # Add specific combos
      - os: ubuntu-latest
        node-version: 22
        coverage: true
    exclude:                          # Remove specific combos
      - os: windows-latest
        node-version: 18

Dynamic Matrix

prepare:
  runs-on: ubuntu-latest
  outputs:
    matrix: ${{ steps.set.outputs.matrix }}
  steps:
    - id: set
      run: echo "matrix=$(jq -c . matrix.json)" >> "$GITHUB_OUTPUT"

test:
  needs: prepare
  strategy:
    matrix: ${{ fromJson(needs.prepare.outputs.matrix) }}

Secrets Management

ScopeAccessUse Case
Repository secretsAll workflows in repoAPI keys, tokens
Environment secretsJobs targeting that environmentProduction credentials
Organization secretsSelected repos in orgShared service accounts
OIDC tokensFederated identityCloud deployment (no stored secrets)

Secrets Best Practices

# Reference secrets - NEVER echo or log them
- run: deploy --token ${{ secrets.DEPLOY_TOKEN }}

# Mask custom values
- run: echo "::add-mask::$CUSTOM_SECRET"

# Use environments for deployment secrets
jobs:
  deploy:
    environment: production           # Requires approval + has secrets
    steps:
      - run: deploy --key ${{ secrets.PROD_API_KEY }}

OIDC for Cloud (No Stored Secrets)

permissions:
  id-token: write
  contents: read

steps:
  - uses: aws-actions/configure-aws-credentials@v4
    with:
      role-to-assume: arn:aws:iam::123456789:role/github-actions
      aws-region: us-east-1

Common Workflow Patterns

Test on Pull Request

name: Test
on:
  pull_request:
    branches: [main]
concurrency:
  group: test-${{ github.head_ref }}
  cancel-in-progress: true
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 run lint
      - run: npm test -- --coverage

Deploy on Merge to Main

name: Deploy
on:
  push:
    branches: [main]
jobs:
  deploy:
    runs-on: ubuntu-latest
    environment: production
    steps:
      - uses: actions/checkout@v4
      - run: npm ci && npm run build
      - run: npx wrangler deploy
        env:
          CLOUDFLARE_API_TOKEN: ${{ secrets.CF_API_TOKEN }}

Release on Tag

name: Release
on:
  push:
    tags: ['v*']
permissions:
  contents: write
jobs:
  release:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with: { fetch-depth: 0 }
      - run: |
          gh release create ${{ github.ref_name }} \
            --generate-notes \
            --title "${{ github.ref_name }}"
        env:
          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Gotchas Table

GotchaProblemFix
Shallow clonegit describe fails, history missingactions/checkout@v4 with fetch-depth: 0
Default permissionsGITHUB_TOKEN is read-only by defaultSet permissions: explicitly
Action pinning@main can break without warningPin to SHA: @abc123 or @v4
Fork PR secretsSecrets unavailable on fork PRsUse pull_request_target carefully
Concurrent deploysRace condition on productionUse concurrency: groups
Stale cachesCache grows unboundedInclude lockfile hash in key
Node.js versionsetup-node defaults varyAlways specify node-version
Docker layer cacheRebuilds everything without cacheUse cache-from: type=gha
Matrix + environmentEach matrix job needs approvalUse a single deploy job after matrix
Path filters + required checksSkipped jobs block mergeUse paths-filter action or make checks non-required
GITHUB_TOKEN in PRsCannot trigger other workflowsUse a PAT or GitHub App token
Windows line endingsScripts fail with \r\nUse .gitattributes or core.autocrlf

Expression Syntax Quick Reference

ExpressionResult
${{ github.event_name }}push, pull_request, etc.
${{ github.ref_name }}Branch or tag name
${{ github.sha }}Full commit SHA
${{ github.actor }}User who triggered
${{ runner.os }}Linux, Windows, macOS
${{ contains(github.event.head_commit.message, '[skip ci]') }}Check commit message
${{ needs.build.outputs.version }}Output from prior job
${{ fromJson(steps.meta.outputs.json) }}Parse JSON output
${{ hashFiles('**/package-lock.json') }}Hash for cache keys
${{ format('refs/heads/{0}', matrix.branch) }}String formatting
${{ toJson(matrix) }}Debug: print matrix config

Step Outputs

steps:
  - id: version
    run: echo "value=$(cat VERSION)" >> "$GITHUB_OUTPUT"

  - run: echo "Version is ${{ steps.version.outputs.value }}"

Job Outputs (for Cross-Job Communication)

jobs:
  build:
    runs-on: ubuntu-latest
    outputs:
      artifact-id: ${{ steps.upload.outputs.artifact-id }}
    steps:
      - id: upload
        run: echo "artifact-id=abc123" >> "$GITHUB_OUTPUT"

  deploy:
    needs: build
    runs-on: ubuntu-latest
    steps:
      - run: echo "Deploying ${{ needs.build.outputs.artifact-id }}"

Reference Files

FileContents
references/github-actions.mdComplete workflow syntax, reusable workflows, composite actions, OIDC, runners, debugging
references/release-automation.mdSemantic versioning, semantic-release, changesets, goreleaser, changelog, publishing
references/testing-pipelines.mdTest stages, parallelism, coverage, service containers, e2e in CI, deployment pipelines

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.