ci-cd-patterns

ci-cd-patterns is a skill for Claude Code from KunanonJ/ai-skills-hub. It costs 41 tokens per session (855 once invoked), scanned A, original, MIT.

A collection of patterns for CI/CD, the automated process that checks code and delivers it to environments such as development, staging, or production. It focuses on GitHub Actions, pull-request checks, deployment workflows, and monitoring.

In plain words
What is it for?
Use it to create or repair GitHub Actions, automate pull-request checks, configure multi-environment deployments, and monitor flaky CI.
Why use it?
It provides repeatable ways to automate linting, tests, builds, deployments, and common pipeline recovery work.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to create or repair GitHub Actions, automate pull-request checks, configure multi-environment deployments, and monitor flaky CI.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kunanonj/ai-skills-hub/ci-cd-patterns
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add KunanonJ/ai-skills-hub --skill ci-cd-patterns
Clone the repo
git clone --depth 1 https://github.com/KunanonJ/ai-skills-hub

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ci-cd-patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/kunanonj/ai-skills-hub/ci-cd-patterns/github.svg)](https://agentmods.dev/skills/kunanonj/ai-skills-hub/ci-cd-patterns)
Your own site
<a href="https://agentmods.dev/skills/kunanonj/ai-skills-hub/ci-cd-patterns"><img src="https://agentmods.dev/badge/skills/kunanonj/ai-skills-hub/ci-cd-patterns/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ci-cd-patterns

Your own site · 80×15
<a href="https://agentmods.dev/skills/kunanonj/ai-skills-hub/ci-cd-patterns"><img src="https://agentmods.dev/badge/skills/kunanonj/ai-skills-hub/ci-cd-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 855 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.00855
Opus 5 $0.00020 $0.00428
Sonnet 5 $0.00008 $0.00171
Haiku 4.5 $0.00004 $0.00085

Measured 9d ago against content hash 331fc2a08afc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ci-cd-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/ci-cd-patterns/SKILL.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CI/CD Patterns

Patterns for GitHub Actions, PR automation, and deployment workflows.

When to Use

  • Setting up or fixing GitHub Actions workflows
  • Automating PR checks (lint, test, build)
  • Configuring deployment pipelines
  • Monitoring PR status and retrying flaky CI
  • Setting up multi-environment deployment (dev, staging, prod)

GitHub Actions --- Common Patterns

Basic CI Workflow

name: CI
on:
  push:
    branches: [main, develop]
  pull_request:
    branches: [main, develop]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Run tests
        run: ./gradlew test

PR Check Workflow

name: PR Check
on: pull_request

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: ./gradlew ktlintCheck

  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: ./gradlew test

  build:
    runs-on: ubuntu-latest
    needs: [lint, test]
    steps:
      - uses: actions/checkout@v4
      - run: ./gradlew build

PR Babysitting Pattern

Monitor a PR through CI, handle common failures:

  1. Check CI status --- gh pr checks <number>
  2. Identify failure type --- flaky test, lint error, build failure
  3. Fix and push --- for lint/build errors, fix locally and push
  4. Retry flaky tests --- re-run the workflow: gh run rerun <run-id> --failed
  5. Resolve merge conflicts --- rebase onto target branch
  6. Enable auto-merge --- gh pr merge <number> --auto --squash

See workflows.md for ready-to-use GitHub Actions YAML templates.

Deployment Checklist

Before deploying:

  • All CI checks pass
  • No merge conflicts
  • Database migrations reviewed (if any)
  • Environment variables set in target environment
  • Rollback plan identified

Gotchas

  • Caching saves minutes per run. Always cache dependencies (actions/cache or actions/setup-java with cache). A cold Gradle build takes 3-5 minutes, cached takes 30 seconds.
  • needs: creates sequential dependencies. Without it, all jobs run in parallel. Use needs: [lint, test] to make build wait for checks.
  • Secret names are case-sensitive. secrets.DB_PASSWORD and secrets.db_password are different. Match the exact name from Settings > Secrets.
  • Don't use actions/checkout@v3 --- use v4. v3 uses Node 16 which is deprecated. v4 uses Node 20.
  • Flaky tests need investigation, not just retry. If you re-run a workflow more than twice for the same test, fix the test. Common causes: race conditions, time-dependent assertions, shared test state.
  • Force-pushing during CI review resets the check suite. Wait for CI to finish before force-pushing, or you'll waste runner minutes.

Read the full file on GitHub · 109 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 109 lines · 41 tokens per session scan A 331fc2a08afc

Subscribe to this mod's changes

ci-cd-patterns is a skill published in the GitHub repository KunanonJ/ai-skills-hub (5 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 855 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

rust-crate-ci

Load before editing any Rust crate in this repo (currently runners/swarm-sandbox-runner). Covers the mandatory local validation gate, common rustfmt/clippy pitfalls, and Windows-specific Rust correctness patterns that CI enforces but are hard to catch locally without a Windows toolchain.

ZaxbyHub/opencode-swarm · 60 tokens

ci-failure-batching

Batch collection and fix protocol for CI failures. Triggered when any CI check fails on a PR. Prevents serial diagnose-fix-push cycles by collecting all failures before fixing.

ZaxbyHub/opencode-swarm · 42 tokens

ci-fix-monitor

Codex adapter for monitoring and fixing CI failures on opencode-swarm PRs. Use when diagnosing failed checks, fixing package-check (npm tarball) failures, resolving quality/lint/format errors, fixing macOS cross-platform file I/O failures, or watching a PR until all checks are green.

ZaxbyHub/opencode-swarm · 68 tokens

swarm-ci-monitor

Codex adapter for end-to-end CI monitoring of an already-reviewed PR in opencode-swarm. Use when the user wants the swarm to monitor a reviewed-and-approved PR's CI, research every failure exhaustively, fix end-to-end, iterate until green (max 5 cycles), then merge. Composes ci-fix-monitor for fix recipes.

ZaxbyHub/opencode-swarm · 75 tokens

tech-debt-ci-review

Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.

ZaxbyHub/opencode-swarm · 61 tokens

devops-cloud

DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.

travisjneuman/.claude · 38 tokens