Maintainer-focused tool for managing CI/CD infrastructure, CTest suites, release packaging, and security automation for iccDEV.

Install

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

Installs to .claude/skills/maintainer-ci-ctest

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.

Maintainer workflow for scoping and updating iccDEV CI, CTest, CPack, sanitizer, workflow, and release-gate infrastructure.
123 charsno explicit “when” trigger
Advanced

Key capabilities

  • →Scope and update iccDEV CI infrastructure
  • →Scope and update CTest infrastructure
  • →Scope and update CPack and release packaging
  • →Scope and update sanitizer helper policy
  • →Scope and update CodeQL/workflow governance
  • →Scope and update security automation

How it works

The skill provides a workflow for iccDEV maintainers to scope and update CI, CTest, CPack, sanitizer, workflow, and release-gate infrastructure.

Inputs & outputs

You give it
Maintainer-owned infrastructure change request
You get back
Updated CI, CTest, CPack, sanitizer, workflow, or release-gate infrastructure

When to use maintainer-ci-ctest

  • →Add or update CTest profile validations
  • →Configure CI workflow gates
  • →Update sanitizer policy and scripts
  • →Manage release packaging and CPack settings

About this skill

Maintainer CI and CTest Workflow

Use this skill only for iccDEV maintainer-owned infrastructure changes: .github/**, Dockerfile*, CTest registration, CPack and release packaging, sanitizer helper policy, CodeQL/workflow governance, vcpkg release verification, and security automation.

General contributor requests should be redirected to issue or PR descriptions unless an iccDEV maintainer explicitly approved the infrastructure change.

Scope Decision

Choose the smallest maintainer-owned surface that proves the behavior:

ChangePrimary locationRequired docs
Add profile inputTesting/CreateAllProfiles.*docs/ctest.md if a scoped generated-profile count changes
Add profile validationTesting/RunTests.*docs/ctest.md if CTest coverage changes
Add focused Linux regression.github/scripts/*.sh.github/ci/regression/README.md or docs/ctest.md
Register CTest suiteBuild/Cmake/Testing/CMakeLists.txtdocs/ctest.md
Change workflow gate.github/workflows/*.ymldocs/regression-workflow-governance.md
Change Apple mobile core gateBuild/Cmake/CMakePresets.json, Build/AppleMobile/**, .github/workflows/ci-apple-*.ymldocs/build.md and docs/regression-workflow-governance.md
Change maintainer DockerfileDockerfile*docs/build.md and docs/regression-workflow-governance.md
Change sanitizer policyBuild/Cmake/CMakeLists.txt, .github/scripts/sanitize-*.github/instructions/*
Change CPack/release packagingBuild/Cmake/**, release workflowsdocs/build.md or release docs
Change vcpkg release verificationports/iccdev/**, vcpkg workflowsvcpkg skill/docs

Keep contributor code changes separate from maintainer infrastructure commits when practical.

CTest Rules

  • check must exist on every platform.
  • check and workflow CTest execution must use --no-tests=error.
  • Unix CTest shell harnesses must run under the Bash 3.2 shipped by macOS as well as current Linux Bash. Avoid mapfile, GNU-only utility flags, and bare empty-array expansion under set -u; keep the generated timeout fallback free of orphaned sleepers and captured termination diagnostics.
  • Do not add hard-coded CTest suite totals to workflows, docs, or maintainer instructions; keep suite lists descriptive and let CTest discovery report the current total.
  • If a change touches legacy packed intent decoding or named-color overprint variants, include both .github/scripts/iccdev-applynamedcmm-cli-args-regression.sh and .github/scripts/iccdev-applysearch-cli-args-regression.sh, plus .github/scripts/iccdev-namedcolor-overprint-regression-tests.sh.
  • Windows full builds include focused executable regressions, batch-backed suites, dump/profile smoke coverage, shared-export coverage, and PAWG report coverage.
  • The comprehensive build matrix must retain MSVC, ClangCL, and MinGW UCRT64 coverage, plus a separate MSVC full CTest gate with warnings treated as errors. Unix must likewise retain the full strict CTest gate.
  • Use rg "Total Tests:|currently register|ci[-]tool[-]tests[.]yml" docs .github before PR handoff to catch stale count and workflow-name references.
  • Generated-profile count changes must update every explicit assertion source, including Build/Cmake/Testing/CMakeLists.txt, generated-profile workflows, and packaged WASM regression scripts.
  • Do not duplicate generated-profile totals in this skill; use the assertion sources as the current truth.
  • Windows batch CTest runs must use the disposable Testing copy under the build tree and must not dirty the source Testing/ directory.
  • Windows executable tests must receive runtime DLL directories through Build/Cmake/Testing/WindowsRuntimePaths.cmake; do not rely on a developer or runner shell PATH for vcpkg or MinGW runtime DLLs.
  • MinGW builds still need UCRT64 bin on the invoking shell PATH because GCC subprocesses such as cc1plus.exe depend on MSYS2 runtime DLLs during build.

Workflow Rules

  • Follow .github/instructions/workflow-governance.instructions.md.
  • Use ci-qa-pr with ctest-mode=full and ctest-recent-limit=0 on the pre-PR branch for the comprehensive build and CTest screening matrix. Pair it with ci-codeql-security on the same head. Complete the applicable local pre-commit and preflight checks first; the maintainer image supplies zizmor, Trivy, CodeQL, fuzzers, Valgrind, and other focused tools. Open a PR only after the pre-PR evidence passes and PR creation is authorized.
  • Treat ci-pr-action as the final PR-head sounding board for merge readiness. Its full scope runs Unix GCC/Clang Release and Debug builds, exact GCC 15.2 strict Release LTO in the regression container, non-sanitized GCC core tool tests, profile builds, representative CTest coverage in both macOS Release/LTO and Debug, and Windows. Its tool-test caller excludes pr-extended CTests; the reusable tool workflow always excludes ci-infrastructure and clusterfuzzlite CTests. It does not replace exhaustive pre-PR screening or local preflight.
  • ci_scope=auto is the default. It selects the full matrix for source, build, and test changes; documentation-only changes use the constrained fast-lane settings. Workflow-only changes keep the core orchestrator limited to setup and finalization while standalone preflight and direct risk analysis provide focused security evidence. Container-only changes use those security gates and local container validation.
  • On synchronize, ci-rebase-safety proves ancestry and ci-pr-action starts its bounded fast lane on the same-repository PR head. This does not fan out the full, sanitizer, JSON, MCP, MATLAB, preflight, or risk-analysis gates. Dispatch final applicable lanes explicitly. Ancestry alone cannot supply PR Summary; completed validation must publish it for the head.
  • ci-pr-risk-security-analysis.yml is directly manually dispatchable. It runs the Linux and Windows workflow-security audits for an explicit final review. Manual audits validate all workflow Bash prologues, not an empty self-diff.
  • ci-matlab is manual-dispatch only. Do not restore its pull-request trigger: its Windows, Linux, macOS, and container lanes are reserved for explicit compatibility validation.
  • Use ci_scope=fast-lane for the exact GCC 15.2 Release LTO and ASAN+UBSAN Release tool lane. Fast lane defaults to the latest CTest with Windows disabled.
  • Container changes require the local canonical-image build and smoke in docs/regression-container.md.
  • Apple mobile core changes must keep the dependency-free apple-*-core presets available, align matching apple-*-extended-core presets with SDK and dependency discovery, and keep simulator app capability/gap reporting in Build/AppleMobile synchronized with docs/build.md.
  • Do not use || true around profile generation, CTest discovery, regression execution, sanitizer checks, or packaging verification.
  • Use least-privilege permissions and credential cleanup.
  • Cache only one immutable download archive per entry, with its SHA-256 in the exact key and verification before extraction. Use explicit restore/save actions; PRs restore only and trusted events save only after a restore miss. Never cache CTest, artifact, or release state. The manual Docker workflow may reuse only inline metadata from a previously validated canonical image resolved to an immutable digest; keep type=gha disabled and retain a no-cache dispatch option.
  • Sanitize all GITHUB_STEP_SUMMARY and GITHUB_OUTPUT writes.
  • Check out the base ref's .github/scripts sparsely and source its sanitizer helpers for every workflow that executes PR-controlled source.
  • Include github.event_name in concurrency keys for workflows that accept both PR and manual-dispatch events, so a manual lane cannot cancel its PR counterpart.
  • Trigger shared-concurrency workflows sequentially to avoid canceling your own run. Use ci-qa-pr for comprehensive pre-PR validation, ci-pr-action for final PR-head validation, and the standalone path-scoped/manual ci-regression-checks workflow for ASAN/UBSAN coverage.
  • For source-coverage workflows, follow .github/skills/code-coverage-analysis/SKILL.md. Use pooled signature-bearing profraw names and llvm-profdata --input-files; never let xargs split one logical report across repeated writes to the same output.

Local Validation

For focused workflow iteration, start with:

.github/scripts/preflight-safety-checks.sh --fast-lane
.github/scripts/check-workflow-cache-policy.sh .github/workflows

This scans changed workflow/script surfaces without running CTest or local CodeQL databases. Run only the nearest feature test during iteration, then use --fast-lane=matlab for MATLAB-only work. Use the full preflight or hosted gates before final handoff.

file <changed-files>
git diff --check
cmake -S Build/Cmake -B build -DENABLE_TOOLS=ON -DENABLE_TESTS=ON -DENABLE_WXWIDGETS=OFF
cmake --build build --parallel "$(nproc)"
ctest --test-dir build -N --no-tests=error
ctest --test-dir build --output-on-failure --no-tests=error

For ci-pr-lint.yml updates, install clang-tidy, clang-tools, and cppcheck, then follow the canonical component-partitioned local reproduction in docs/build.md#maintainer-static-analysis. Verify that every selected component has its own cppcheck and clang-tidy report, and that the combined reports preserve the sum of the component output.

For workflow YAML:

python3 -c "import yaml; [yaml.safe_load(open(p)) for p in ['.github/workflows/<workflow>.yml']]; print('YAML parse OK')"
jactionlint --profile correctness --no-color .github/workflows/<workflow>.yml
python3 .github/scripts/check-workflow-fixed-output-batching.py \
  .github/workflows/<workflow>.ym

---

*Content truncated.*

When not to use it

  • →For general contributor requests
  • →When not making maintainer-owned infrastructure changes
  • →When not explicitly approved by an iccDEV maintainer

Limitations

  • →Use this skill only for iccDEV maintainer-owned infrastructure changes:
  • →General contributor requests should be redirected to issue or PR descriptions unless an iccDEV maintainer explicitly approved the infrastructure change.
  • →Do not add hard-coded CTest suite totals to workflows, docs, or maintainer instructions

How it compares

This skill offers a specialized workflow for maintainer-owned infrastructure changes, ensuring adherence to specific rules and validation steps, unlike general CI/CD pipeline management.

Compared to similar skills

maintainer-ci-ctest side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
maintainer-ci-ctest (this skill)04moReviewAdvanced
deployment-pipeline-design66moReviewAdvanced
cloudflare-deploy39moReviewIntermediate
artifactory-module-architecture46moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

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.

670

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.

342

artifactory-module-architecture

TencentBlueKing

Artifactory 制品库模块架构指南,涵盖制品上传下载、存储后端适配、制品元数据、清理策略、权限控制。当用户开发制品库功能、处理制品存储、配置清理策略或实现制品管理时使用。

419

deployment-engineer

sickn33

Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization. Use PROACTIVELY for CI/CD design, GitOps implementation, or deployment automation.

418

genkit-infra-expert

jeremylongshore

Execute use when deploying Genkit applications to production with Terraform. Trigger with phrases like "deploy genkit terraform", "provision genkit infrastructure", "firebase functions terraform", "cloud run deployment", or "genkit production infrastructure". Provisions Firebase Functions, Cloud Run services, GKE clusters, monitoring dashboards, and CI/CD for AI workflows.

15

managing-deployment-rollbacks

jeremylongshore

Deploy use when you need to work with deployment and CI/CD. This skill provides deployment automation and orchestration with comprehensive guidance and automation. Trigger with phrases like "deploy application", "create pipeline", or "automate deployment".

11

Search skills

Search the agent skills registry