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.zipInstalls 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.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
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
| Workflow | Trigger | Purpose |
|---|---|---|
ci.yml | PR to main/release-*, merge_group, workflow_dispatch | Main CI: checks + build + test |
lint-format.yml | PR to main, merge_group | goimports, gofumpt, golangci-lint, actionlint |
regression.yml | Daily cron (03:00 UTC), manual | Multi-K8s-version regression |
image-promotion.yml | Push to main/release-* | Post-merge image tagging + scanning |
release.yml | Manual dispatch | Full release orchestrator |
build-base-images.yml | Weekday cron (04:30 UTC) | Rebuilds all base images |
Release Sub-Workflows (called by release.yml)
| Workflow | Purpose |
|---|---|
oss-release.yml | OSS image release |
plus-release.yml | Plus/NAP image release |
publish-helm.yml | Helm chart publishing to registry |
Reusable Build Workflows (called via workflow_call)
| Workflow | Purpose |
|---|---|
build-artifacts.yml | Orchestrates GoReleaser binary builds + image matrix |
build-oss.yml | Builds single OSS image variant |
build-plus.yml | Builds single Plus/NAP image variant |
build-test-image.yml | Builds Python e2e test image |
setup-smoke.yml | Sets up and runs smoke tests |
patch-image.yml | OS-level patches on existing images |
retag-images.yml | Re-tags images in GCR Dev Registry |
Security & Compliance
| Workflow | Purpose |
|---|---|
codeql-analysis.yml | GitHub CodeQL scanning |
scorecards.yml | OpenSSF Scorecards |
dependency-review.yml | Dependency review for PRs |
certify-ubi-image.yml | Red 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-plusmatrix-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 matricesmatrix-regression.json: Regression test matrix (K8s version combinations)patch-images.json: Patch image definitions forpatch-image.yml
Caching Strategy
- Go binaries: cached by
go_code_md5hash - Docker images: cached by
docker_md5hash - 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/amd64only -- do not addarm64to NAP matrices - Renovate manages tool versions via
# renovate:comments -- do not update manually image-promotion.ymlruns on merge tomain, not on PR -- don't expect images from PRs
When not to use it
- →Modifying repository secrets
Prerequisites
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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| nic-ci-pipelines (this skill) | 0 | 2mo | No flags | Advanced |
| bazel-build-optimization | 14 | 2mo | No flags | Advanced |
| linkerd-patterns | 6 | 5mo | Review | Advanced |
| deployment-pipeline-design | 6 | 2mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
bazel-build-optimization
wshobson
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
linkerd-patterns
wshobson
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
k8s-helm
rohitg00
Manage Helm charts, releases, and repositories. Use for Helm installations, upgrades, rollbacks, chart development, and release management.
cloudflare-deploy
davila7
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
gitlab-ci-patterns
wshobson
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.