Source profileQuality 94/100

laurigates/claude-plugins/configure-plugin/skills/ci-workflows/SKILL.md

ci-workflows

GitHub Actions workflow standards. Use when checking CI/CD compliance, referencing canonical workflow shapes, or another skill needs workflow structure guidance.

Source repository stars
53
Declared platforms
0
Static risk flags
0
Last source update
2026-08-24
Source checked
2026-08-25

Decision brief

What it does: where it fits

GitHub Actions workflow standards.

Best for

  • Use when checking CI/CD compliance, referencing canonical workflow shapes, or another skill needs workflow structure guidance.

Not for

  • Build Failing
  • Multi-Platform Issues

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/laurigates/claude-plugins --skill "configure-plugin/skills/ci-workflows"
Safe inspection promptEditorial

Inspect the Agent Skill "ci-workflows" from https://github.com/laurigates/claude-plugins/blob/5de06622d8def8c36f7f39d980300aaa15af4357/configure-plugin/skills/ci-workflows/SKILL.md at commit 5de06622d8def8c36f7f39d980300aaa15af4357. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    1. Container Build Workflow

    File: .github/workflows/container-build.yml

    Multi-platform builds (amd64, arm64)GitHub Container Registry (GHCR)Semantic version tagging
  2. 02

    2. Release Please Workflow

    File: .github/workflows/release-please.yml

    File: .github/workflows/release-please.ymlSee configure-release-please (its REFERENCE.md carries the standard workflow, token, and config templates) for details.
  3. 03

    3. ArgoCD Auto-merge Workflow (Optional)

    File: .github/workflows/argocd-automerge.yml

    Triggers on image-updater- branches from ArgoCD Image UpdaterCreates PR automatically if not existsSelf-approval with optional PAT (for bypassing GitHub restrictions)
  4. 04

    4. Test Workflow (Recommended)

    File: .github/workflows/test.yml

    File: .github/workflows/test.yml
  5. 05

    5. Claude Auto-Fix Workflow (Optional)

    File: .github/workflows/claude-auto-fix.yml

    Triggers on workflowrun completion for monitored workflowsGathers failure logs and context automaticallyDeduplication: caps open auto-fix PRs at 3

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score94/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars53SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
laurigates/claude-plugins
Skill path
configure-plugin/skills/ci-workflows/SKILL.md
Commit
5de06622d8def8c36f7f39d980300aaa15af4357
License
MIT
Collected
2026-08-25
Default branch
main
View the original SKILL.md

CI Workflow Standards

When to Use This Skill

Use this skill when...Use a sibling skill instead when...
You need the canonical GitHub Actions workflow shapes (container build, test, release)You want to audit or install workflows end-to-end as an interactive workflow — use configure-workflows
You are checking whether existing .github/workflows/*.yml follows the documented conventionsYou want pre-built reusable callers wired up — use configure-reusable-workflows
Another skill needs to cite the standard workflow structureThe user asked you to actually create or repair CI workflows

Version: 2025.1

Standard GitHub Actions workflows for CI/CD automation.

Display name convention

Every workflow's name: follows <Domain>: <Action> [<target>] so the GitHub Actions sidebar groups related workflows alphabetically. Quote the value because YAML treats : inside an unquoted scalar as a key separator. See .claude/rules/workflow-naming.md for the canonical rule, the active domain list, and the cross-workflow rename procedure. Mirror the pattern in any workflow you scaffold here.

Required Workflows

1. Container Build Workflow

File: .github/workflows/container-build.yml

Multi-platform container build with GHCR publishing:

name: "Container: Build"

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]
  release:
    types: [published]

env:
  REGISTRY: ghcr.io
  IMAGE_NAME: ${{ github.repository }}

jobs:
  build:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      packages: write

    steps:
      - uses: actions/checkout@v6

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v4

      - name: Log in to Container Registry
        if: github.event_name != 'pull_request'
        uses: docker/login-action@v4
        with:
          registry: ${{ env.REGISTRY }}
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}

      - name: Extract metadata
        id: meta
        uses: docker/metadata-action@v6
        with:
          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
          tags: |
            type=ref,event=branch
            type=ref,event=pr
            type=semver,pattern={{version}}
            type=semver,pattern={{major}}.{{minor}}

      - name: Build and push
        uses: docker/build-push-action@v7
        with:
          context: .
          platforms: linux/amd64,linux/arm64
          push: ${{ github.event_name != 'pull_request' }}
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}
          cache-from: type=gha
          cache-to: type=gha,mode=max
          build-args: |
            SENTRY_AUTH_TOKEN=${{ secrets.SENTRY_AUTH_TOKEN }}

Key features:

  • Multi-platform builds (amd64, arm64)
  • GitHub Container Registry (GHCR)
  • Semantic version tagging
  • Build caching with GitHub Actions cache
  • Sentry integration for source maps

2. Release Please Workflow

File: .github/workflows/release-please.yml

See configure-release-please (its REFERENCE.md carries the standard workflow, token, and config templates) for details.

3. ArgoCD Auto-merge Workflow (Optional)

File: .github/workflows/argocd-automerge.yml

Auto-merge PRs from ArgoCD Image Updater branches:

name: "Image Updater: Auto-merge"

on:
  push:
    branches:
      - 'image-updater-**'

permissions:
  contents: write
  pull-requests: write

jobs:
  create-and-merge:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6

      - name: Create Pull Request
        id: create-pr
        env:
          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: |
          PR_URL=$(gh pr create \
            --base main \
            --head "${{ github.ref_name }}" \
            --title "chore(deps): update container image" \
            --body "Automated image update by argocd-image-updater.

          Branch: \`${{ github.ref_name }}\`" \
            2>&1) || true

          if echo "$PR_URL" | grep -q "already exists"; then
            PR_URL=$(gh pr view "${{ github.ref_name }}" --json url -q .url)
          fi

          echo "pr_url=$PR_URL" >> "$GITHUB_OUTPUT"

      - name: Approve PR
        env:
          GH_TOKEN: ${{ secrets.AUTO_MERGE_PAT || secrets.GITHUB_TOKEN }}
        run: gh pr review --approve "${{ github.ref_name }}"
        continue-on-error: true

      - name: Enable auto-merge
        env:
          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: gh pr merge --auto --squash "${{ github.ref_name }}"

Key features:

  • Triggers on image-updater-** branches from ArgoCD Image Updater
  • Creates PR automatically if not exists
  • Self-approval with optional PAT (for bypassing GitHub restrictions)
  • Squash merge with auto-merge enabled

Prerequisites:

  • Enable auto-merge in repository settings
  • Optional: AUTO_MERGE_PAT secret for self-approval

4. Test Workflow (Recommended)

File: .github/workflows/test.yml

name: "Test: Suite"

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

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6

      - name: Setup Node.js
        uses: actions/setup-node@v6
        with:
          node-version: '22'
          cache: 'npm'

      - name: Install dependencies
        run: npm ci

      - name: Run linter
        run: npm run lint

      - name: Run type check
        run: npm run typecheck

      - name: Run tests
        run: npm run test:coverage

      - name: Upload coverage
        uses: codecov/codecov-action@v6
        with:
          files: ./coverage/lcov.info

5. Claude Auto-Fix Workflow (Optional)

File: .github/workflows/claude-auto-fix.yml

Automated CI failure analysis and remediation using Claude Code Action:

name: "Auto-fix: CI failures"

on:
  workflow_run:
    # Customize: list the CI workflow display names to monitor.
    # The strings here must match the target workflows' `name:` values exactly.
    workflows: ["Test: Suite"]
    types: [completed]
  workflow_dispatch:
    inputs:
      run_id:
        description: "Failed workflow run ID to analyze"
        required: true
        type: string

concurrency:
  group: auto-fix-${{ github.event.workflow_run.head_branch || github.ref_name }}
  cancel-in-progress: false

Key features:

  • Triggers on workflow_run completion for monitored workflows
  • Gathers failure logs and context automatically
  • Deduplication: caps open auto-fix PRs at 3
  • Loop prevention: skips commits starting with fix(auto):
  • Auto-fixable failures get a fix PR; complex failures get a GitHub issue
  • Uses anthropics/claude-code-action@v1 with scoped tool permissions

Prerequisites:

  • CLAUDE_CODE_OAUTH_TOKEN secret configured in repository settings
  • At least one CI workflow to monitor (customize workflows: list)

For the full template, see the Claude Auto-Fix Workflow Template in configure-workflows.

Workflow Standards

Action Versions

ActionVersionPurpose
actions/checkoutv6Repository checkout
docker/setup-buildx-actionv4Multi-platform builds
docker/login-actionv4Registry authentication
docker/metadata-actionv6Image tagging
docker/build-push-actionv7Container build/push
actions/setup-nodev6Node.js setup
googleapis/release-please-actionv5Release automation

Permissions

Minimal permissions required:

permissions:
  contents: read      # Default for most jobs
  packages: write     # For container push to GHCR
  pull-requests: write  # For release-please PR creation

Triggers

Standard trigger patterns:

# Build on push and PR to main
on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

# Also build on release
on:
  release:
    types: [published]

Build Caching

Use GitHub Actions cache for Docker layers:

cache-from: type=gha
cache-to: type=gha,mode=max

Multi-Platform Builds

Build for both amd64 and arm64:

platforms: linux/amd64,linux/arm64

Compliance Requirements

Required Workflows

WorkflowPurposeRequired
container-buildContainer buildsYes (if Dockerfile)
release-pleaseAutomated releasesYes
testTesting and lintingRecommended
argocd-automergeAuto-merge image updatesOptional (if using ArgoCD Image Updater)
claude-auto-fixAutomated CI failure remediationOptional

Required Elements

ElementRequirement
checkout actionv6
build-push actionv7
Multi-platformamd64 + arm64
CachingGHA cache enabled
PermissionsExplicit and minimal

Status Levels

StatusCondition
PASSAll required workflows present with compliant config
WARNWorkflows present but using older action versions
FAILMissing required workflows
SKIPNot applicable (no Dockerfile = no container-build)

Secrets Required

SecretPurposeRequired
GITHUB_TOKENContainer registry authAuto-provided
SENTRY_AUTH_TOKENSource map uploadIf using Sentry
MY_RELEASE_PLEASE_TOKENRelease PR creationFor release-please
CLAUDE_CODE_OAUTH_TOKENClaude Code Action authFor claude-auto-fix

Troubleshooting

Build Failing

  • Check Dockerfile syntax
  • Verify build args are passed correctly
  • Check cache invalidation issues

Multi-Platform Issues

  • Ensure Dockerfile is platform-agnostic
  • Use official multi-arch base images
  • Avoid architecture-specific binaries

Cache Not Working

  • Verify cache-from and cache-to are set
  • Check GitHub Actions cache limits (10GB)
  • Consider registry-based caching for large images

Frequently asked questions

What to verify before installation and use

What does the ci-workflows source document cover?

GitHub Actions workflow standards.

How do I install ci-workflows?

The source record exposes this install command: npx skills add https://github.com/laurigates/claude-plugins --skill "configure-plugin/skills/ci-workflows". Inspect the command and pinned source before running it.

Alternatives

Compare before choosing