NI

nic-ci-pipelines

Provides access to the architecture, workflows, and build patterns for the NIC CI/CD system on GitHub Actions.

Install

mkdir -p .claude/skills/nic-ci-pipelines && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10137" && unzip -o skill.zip -d .claude/skills/nic-ci-pipelines && rm skill.zip

Installs to .claude/skills/nic-ci-pipelines

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

CI/CD pipeline structure, GitHub Actions workflows, reusable workflow patterns, and matrix builds for NIC. Use when working on CI workflows, debugging build failures, adding new workflow steps, modifying build matrices, or understanding the release pipeline.
258 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Advanced

Key capabilities

  • Debug CI build failures
  • Modify workflow steps
  • Adjust build matrices
  • Understand release pipelines
  • Manage reusable workflows

How it works

It provides context on the composition of reusable workflows, helping to debug failures and manage build matrices.

Inputs & outputs

You give it
CI/CD workflow issue
You get back
Pipeline fix or explanation

When to use nic-ci-pipelines

  • Debugging a CI build failure
  • Adding a new step to the CI pipeline
  • Modifying the build matrix for new variants

About this skill

NIC CI/CD Pipelines

Workflow Architecture

The CI system uses GitHub Actions with extensive reusable workflow composition.

ci.yml (main CI orchestrator)
  -> checks (format, lint, codegen, CRDs, chart version)
  -> unit-tests
  -> build-artifacts.yml (reusable)
       -> build-oss.yml (per-variant, matrix)
       -> build-plus.yml (per-variant, matrix)  <- also used for NAP variants
  -> helm-tests
  -> setup-smoke.yml (reusable)
  -> e2e tests

image-promotion.yml (post-merge)
  -> builds images, tags edge/stable
  -> Trivy + DockerScout security scans
  -> publishes edge Helm charts

release.yml (manual dispatch)
  -> oss-release.yml
  -> plus-release.yml
  -> publish-helm.yml
  -> certify-ubi-image.yml
  -> marketplace pushes (AWS, Azure, GCP)

Key Workflows

WorkflowTriggerPurpose
ci.ymlPR to main/release-*, merge_group, workflow_dispatchMain CI: checks + build + test
lint-format.ymlPR to main, merge_groupgoimports, gofumpt, golangci-lint, actionlint
regression.ymlDaily cron (03:00 UTC), manualMulti-K8s-version regression
image-promotion.ymlPush to main/release-*Post-merge image tagging + scanning
release.ymlManual dispatchFull release orchestrator
build-base-images.ymlWeekday cron (04:30 UTC)Rebuilds all base images

Release Sub-Workflows (called by release.yml)

WorkflowPurpose
oss-release.ymlOSS image release
plus-release.ymlPlus/NAP image release
publish-helm.ymlHelm chart publishing to registry

Reusable Build Workflows (called via workflow_call)

WorkflowPurpose
build-artifacts.ymlOrchestrates GoReleaser binary builds + image matrix
build-oss.ymlBuilds single OSS image variant
build-plus.ymlBuilds single Plus/NAP image variant
build-test-image.ymlBuilds Python e2e test image
setup-smoke.ymlSets up and runs smoke tests
patch-image.ymlOS-level patches on existing images
retag-images.ymlRe-tags images in GCR Dev Registry

Security & Compliance

WorkflowPurpose
codeql-analysis.ymlGitHub CodeQL scanning
scorecards.ymlOpenSSF Scorecards
dependency-review.ymlDependency review for PRs
certify-ubi-image.ymlRed Hat UBI certification for OpenShift

CI Patterns

Matrix Builds

Image variants are defined in JSON under .github/data/:

  • matrix-images-oss.json: debian, alpine, ubi (amd64 + arm64)
  • matrix-images-plus.json: debian-plus, alpine-plus, alpine-plus-fips, ubi-10-plus
  • matrix-images-nap.json: WAF v4/v5, DoS, UBI 10 (amd64 only)
  • matrix-smoke-oss.json, matrix-smoke-plus.json, matrix-smoke-nap.json: Smoke test matrices
  • matrix-regression.json: Regression test matrix (K8s version combinations)
  • patch-images.json: Patch image definitions for patch-image.yml

Caching Strategy

  • Go binaries: cached by go_code_md5 hash
  • Docker images: cached by docker_md5 hash
  • Stable images in GCR are checked before rebuilding

Fork Awareness

forked_workflow variable gates authenticated operations. Forked PRs get local-only builds without secret access.

Concurrency

Each workflow uses group: ${{ github.ref_name }}-<suffix> with cancel-in-progress: true.

Secrets

Retrieved from Azure Key Vault via OIDC -- not stored as GitHub secrets directly.

Version Source of Truth

.github/data/version.txt contains IC_VERSION and HELM_CHART_VERSION.


Gotchas

  • Never add secrets as GitHub repository secrets -- use Azure Key Vault OIDC flow
  • Always pin GitHub Actions to immutable SHA hashes, not mutable tags
  • Matrix JSON files in .github/data/ must stay in sync with Makefile image targets
  • NAP variants are linux/amd64 only -- do not add arm64 to NAP matrices
  • Renovate manages tool versions via # renovate: comments -- do not update manually
  • image-promotion.yml runs on merge to main, not on PR -- don't expect images from PRs

When not to use it

  • Modifying repository secrets

Prerequisites

GitHub Actions

Limitations

  • Requires understanding of reusable workflow composition

How it compares

It offers deep insight into a complex, composition-heavy CI/CD architecture, rather than just general GitHub Actions help.

Compared to similar skills

nic-ci-pipelines side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
nic-ci-pipelines (this skill)02moNo flagsAdvanced
bazel-build-optimization142moNo flagsAdvanced
linkerd-patterns65moReviewAdvanced
deployment-pipeline-design62moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry