New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Regression Workflow Governance

by InternationalColorConsortium in InternationalColorConsortium/iccDEV

Add or update iccDEV regression gates and tool-test workflow coverage while preserving GitHub Actions governance, sanitizer reporting, and issue traceability.

BSD-3-ClauseAuto-check passedDevOps & Cloud

Install Regression Workflow Governance

skills CLI
$ npx skills add InternationalColorConsortium/iccDEV --skill regression-workflow-governance -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install InternationalColorConsortium/iccDEV regression-workflow-governance --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/InternationalColorConsortium/iccDEV.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/regression-workflow-governance .claude/skills/regression-workflow-governance && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
regression-workflow-governance
GitHub stars
183
Token cost
~1.2k tokens
SKILL.md length
412 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

Add or update iccDEV regression gates and tool-test workflow coverage while preserving GitHub Actions governance, sanitizer reporting, and issue traceability.

  • Works in 4 steps: Issue or PR reference, for example #928. → The exact affected component path. → The smallest reproducible input or… → …
  • Tasks that involve CI/CD
  • SKILL.md covers Required Inputs, Workflow, Validation and Review Checklist, plus 1 more section
  • Calls python3, bash and git

What it does

Regression Workflow Governance is an agent skill from InternationalColorConsortium/iccDEV. Add or update iccDEV regression gates and tool-test workflow coverage while preserving GitHub Actions governance, sanitizer reporting, and issue traceability.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering CI/CD. It works with GitHub Actions and GitHub. The repository describes itself as: iccDEV provides a set of libraries and tools that allow for the interaction, manipulation, and application of ICC color management profiles. The licence is BSD-3-Clause.

When your agent uses it

  • Tasks that involve CI/CD

Example prompts

  • “/regression-workflow-governance”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): bash, read, grep, glob, shell(git:*)

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Issue or PR reference, for example #928.
  2. The exact affected component path.
  3. The smallest reproducible input or generated-profile invariant.
  4. The expected pass/fail signal.

What it can do on your machine

Read from SKILL.md and the folder at commit 3c2425d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • bash
    • read
    • grep
    • glob
    • shell(git:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3
    • bash
    • git
    • actionlint

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Regression Workflow Governance loads about 1.2k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 412 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from InternationalColorConsortium/iccDEV at commit 3c2425d, republished under its BSD-3-Clause licence (© InternationalColorConsortium). 412 words, ~1,153 tokens.

Download SKILL.mdSave it as .claude/skills/regression-workflow-governance/SKILL.md (or your agent's skills folder).
name
regression-workflow-governance
description
Add or update iccDEV regression gates and tool-test workflow coverage while preserving GitHub Actions governance, sanitizer reporting, and issue traceability.
allowed-tools
bash, read, grep, glob, shell(git:*)

Regression Workflow Governance

Use this skill when adding regression coverage or changing ci-iccdev-tool-tests.yml.

Required Inputs

  1. Issue or PR reference, for example #928.
  2. The exact affected component path.
  3. The smallest reproducible input or generated-profile invariant.
  4. The expected pass/fail signal.

Workflow

  1. Read ../../../docs/regression-workflow-governance.md.
  2. Put reusable checks in .github/scripts/ when the logic is more than a few shell lines or should run in more than one workflow.
  3. Wire the check into the nearest existing regression block:
    • ci-iccdev-tool-tests.yml for the main ASAN/UBSAN tool gate.
    • Other workflows only when they own the affected platform or feature.
  4. Label the sub-test with the issue number and a short technical purpose.
  5. Keep run: blocks compliant with workflow governance: set -euo pipefail, credential cleanup, no direct ${{ }} in shell, trusted-base helpers for PR workflows, and sanitized summary output.
  6. Update .github/ci/regression/README.md or the relevant docs so future maintainers can find the gate.
  7. If a GitHub Actions run URL is involved, download the full run log archive and audit all jobs, including green jobs, for hidden diagnostics.
  8. Run local script syntax checks and the focused regression before handoff. If the regression is added inside iccdev-tool-coverage-baseline.sh, run the direct script and the CTest wrapper because the CTest suite count should stay unchanged.

Validation

bash
bash -n .github/scripts/<new-regression>.sh
git diff --check
file .github/scripts/<new-regression>.sh

For local tool gates, set paths explicitly:

bash
ICCDEV_TOOLS_DIR=$PWD/Build/Tools \
ICCDEV_TESTING_DIR=$PWD/Testing \
ICCDEV_TEST_OUTDIR=/tmp/iccdev-regression \
  .github/scripts/<new-regression>.sh

For edits to the existing tool coverage script:

bash
ICCDEV_TOOLS_DIR=$PWD/build/Tools \
ICCDEV_TESTING_DIR=$PWD/Testing \
ICCDEV_TEST_OUTDIR=/tmp/iccdev-tool-output \
  .github/scripts/iccdev-tool-coverage-baseline.sh --asan --quick
ctest --test-dir build -R '^iccdev\.tool-coverage$' --output-on-failure

For workflow and packaging changes:

bash
python3 -c "import yaml; [yaml.safe_load(open(p)) for p in ['.github/workflows/ci-pr-action.yml','.github/workflows/ci-iccdev-tool-tests.yml']]; print('YAML parse OK')"
actionlint -no-color .github/workflows/<workflow>.yml
python3 .github/scripts/audit-workflow-permissions.py --workflows-dir .github/workflows --format shell

If CMake or C++ changed, also run:

bash
.github/scripts/run-codeql-local.sh --custom-only
Show full SKILL.md (173 more words)Show less

Review Checklist

  • The test fails on the vulnerable or non-canonical behavior and passes on the patch.
  • Output names include the issue number or regression name.
  • Exit codes distinguish graceful tool failure from signal crashes.
  • ASAN/UBSAN findings are treated as failures except for documented benign suppressions.
  • Workflow changes follow .github/instructions/workflow-governance.instructions.md.
  • PR workflow helper trust boundaries follow docs/workflow-security-trust-boundaries.md.
  • Pull request review follows docs/governance/UPSTREAM_PR_READINESS.md: request review only for a frozen head with current evidence, review the complete PR and contract matrix rather than incremental slices, and stop serial automated review when a re-review finds any new blocker.
  • The PR was checked against the repeat-review findings in docs/regression-workflow-governance.md: scope split, script headers, trigger parity, trusted-base helpers, exact SHA validation, input rejection, timeout bounds, reproducible docs, and temporary-artifact cleanup.
  • Green workflow runs were checked for hidden log diagnostics, not only failed annotations.
  • Any duplicate install manifest, missing-file uninstall, vcpkg CRT, vcpkg root, apt cache, Homebrew annotation, or skipped smoke coverage issue has either a hard gate or a documented reason for deferral.

References

  • ../../../docs/regression-workflow-governance.md
  • ../../../docs/workflow-security-trust-boundaries.md
  • ../../instructions/workflow-governance.instructions.md
  • ../../instructions/testing.instructions.md
  • ../../prompts/add-regression-workflow.prompt.md

© InternationalColorConsortium, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/regression-workflow-governance of InternationalColorConsortium/iccDEV.

Open the folder on GitHubat commit 3c2425d

Compare with similar skills

Regression Workflow Governance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Regression Workflow Governance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Regression Workflow Governance this skillInternationalColorConsortium/iccDEV183—~1.2kAutomated safety check: PassBSD-3-Clause
Nushellccusage/ccusage19k—~938Automated safety check: PassCustom licence
Make GitHub Actions Workflowdotnet/efcore15k—~2.1kAutomated safety check: PassMIT
AI News RadarLearnPrompt/ai-news-radar1.8k—~2.5kAutomated safety check: NotesMIT
Clawsweeperopenclaw/openclaw392k—~3kAutomated safety check: PassMIT
ONNX Runtime CI Managementmicrosoft/onnxruntime22k—~4.1kAutomated safety check: PassMIT

Similar skills

  • Nushell

    ccusage/ccusage

    Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.

    19k GitHub stars~938 tokensUpdated today
    DevOps & CloudAuto-check passed

  • Make GitHub Actions Workflow

    dotnet/efcore

    Official

    Create GitHub Actions workflows for CI, automation, or PR management.

    15k GitHub stars~2.1k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • AI News Radar

    LearnPrompt/ai-news-radar

    A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…

    1.8k GitHub stars~2.5k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Clawsweeper

    openclaw/openclaw

    A skill your agent uses for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed…

    392k GitHub stars~3k tokensUpdated today
    DevOps & CloudAuto-check passed

  • ONNX Runtime CI Management

    microsoft/onnxruntime

    Official

    Triggers, re-runs and unblocks the CI checks on an ONNX Runtime pull request, after diagnosing whether a failure is transient or needs a code change.

    22k GitHub stars~4.1k tokensUpdated today
    DevOps & CloudAuto-check passed

  • CI Watchdog

    latitude-dev/latitude-llm

    Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.

    4.7k GitHub stars~1.6k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

More from InternationalColorConsortium/iccDEV

All 23 skills in this repo

  • Afl Smoke

    InternationalColorConsortium/iccDEV

    Run or update the iccDEV AFL++ manual smoke workflow, seeds, and maintainer documentation.

    183 GitHub stars~1.7k tokensUpdated 2 days ago
    Auto-check passed

  • Avx2 Clut Diagnostics

    InternationalColorConsortium/iccDEV

    Diagnose runtime-dispatched AVX2 3D CLUT interpolation, collect trace evidence, validate vector and masked-tail output, and prepare optimization handoff data.

    183 GitHub stars~850 tokensUpdated 2 days ago
    Auto-check passed

  • Clusterfuzzlite

    InternationalColorConsortium/iccDEV

    Build, test, or update the iccDEV ClusterFuzzLite libFuzzer integration across ASan, UBSan, and MSan.

    183 GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed

  • iOS Clut Editor

    InternationalColorConsortium/iccDEV

    Build, review, and maintain the ios-clut-editor profile and 3D CLUT editing proof-of-concept app without repeating prior iOS review-loop failures.

    183 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • iOS Manual Examples

    InternationalColorConsortium/iccDEV

    Maintain the manual iOS example app CMake projects, local Xcode build helpers, device signing guard rails, and documentation.

    183 GitHub stars~796 tokensUpdated 2 days ago
    Auto-check passed

  • JSON Config Regression

    InternationalColorConsortium/iccDEV

    Validate iccDEV JSON/profile config parser changes with fail-closed regression gates and CLI exercises.

    183 GitHub stars~469 tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Regression Workflow Governance

What does Regression Workflow Governance do?

Add or update iccDEV regression gates and tool-test workflow coverage while preserving GitHub Actions governance, sanitizer reporting, and issue traceability. Regression Workflow Governance is an agent skill from InternationalColorConsortium/iccDEV. Add or update iccDEV regression gates and tool-test workflow coverage while preserving GitHub Actions governance, sanitizer reporting, and issue traceability.

When should I use Regression Workflow Governance?

Regression Workflow Governance fits situations like: tasks that involve CI/CD.

How do I install Regression Workflow Governance in Claude Code?

Run `npx skills add InternationalColorConsortium/iccDEV --skill regression-workflow-governance -a claude-code`. Or copy the skill folder (.github/skills/regression-workflow-governance in InternationalColorConsortium/iccDEV) into .claude/skills/regression-workflow-governance in your project. Claude Code loads it when a task matches its description.

How do I install Regression Workflow Governance in Codex?

Run `npx skills add InternationalColorConsortium/iccDEV --skill regression-workflow-governance -a codex`. Or copy the skill folder (.github/skills/regression-workflow-governance in InternationalColorConsortium/iccDEV) into .agents/skills/regression-workflow-governance in your project. Codex loads it when a task matches its description.

Can I use Regression Workflow Governance in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add InternationalColorConsortium/iccDEV --skill regression-workflow-governance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/regression-workflow-governance, .gemini/skills/regression-workflow-governance, .github/skills/regression-workflow-governance and .opencode/skills/regression-workflow-governance in your project.

What does Regression Workflow Governance need to run?

Going by SKILL.md and its folder, Regression Workflow Governance needs the command-line tools its instructions call (python3, bash, git and actionlint). Our summary lists: Python 3. Its frontmatter pre-approves these tools: bash, read, grep, glob, shell(git:*).

Does Regression Workflow Governance access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Regression Workflow Governance safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Regression Workflow Governance use?

Regression Workflow Governance is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Regression Workflow Governance use?

About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Regression Workflow Governance?

Skills that share tags, products or a category with Regression Workflow Governance: Nushell (ccusage/ccusage, 19k stars), Make GitHub Actions Workflow (dotnet/efcore, 15k stars), AI News Radar (LearnPrompt/ai-news-radar, 1.8k stars) and Clawsweeper (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Regression Workflow Governance?

InternationalColorConsortium (a GitHub organization) maintains it in InternationalColorConsortium/iccDEV, which has 183 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 9, 2026.

Source: InternationalColorConsortium/iccDEV on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.