Agent skill

Regression Container Maintainer

by InternationalColorConsortium in InternationalColorConsortium/iccDEV

Use the published unified iccDEV container for maintainer smoke testing, pull request validation, issue reproduction, sanitizer review, and CI handoff.

BSD-3-ClauseAuto-check passedDevelopment

Install Regression Container Maintainer

skills CLI
$ npx skills add InternationalColorConsortium/iccDEV --skill regression-container-maintainer -a claude-code

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

GitHub CLI
$ gh skill install InternationalColorConsortium/iccDEV regression-container-maintainer --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-container-maintainer .claude/skills/regression-container-maintainer && 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-container-maintainer
GitHub stars
183
Token cost
~1.1k tokens
SKILL.md length
534 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

Use the published unified iccDEV container for maintainer smoke testing, pull request validation, issue reproduction, sanitizer review, and CI handoff.

  • Works in 6 steps: Operation: basic smoke, PR validation,… → Image selector: choose latest,… → PR, issue, branch, or commit reference. → …
  • Tasks that involve Pull requests
  • SKILL.md covers Required Inputs, Workflow, Safety Gates and References
  • Calls python3 and git

What it does

Regression Container Maintainer is an agent skill from InternationalColorConsortium/iccDEV. Use the published unified iccDEV container for maintainer smoke testing, pull request validation, issue reproduction, sanitizer review, and CI handoff.

Its SKILL.md is about 1.1k 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 Development, covering Pull requests. 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 Pull requests

Example prompts

  • “/regression-container-maintainer”

Requirements

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

Workflow steps

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

  1. Operation: basic smoke, PR validation, or issue reproduction.
  2. Image selector: choose latest, ci-qa-pr-docker-testing,
  3. PR, issue, branch, or commit reference.
  4. Affected tool and smallest focused regression.
  5. Expected pass and failure signals.
  6. Host evidence directory.

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:*)
    • shell(docker:*)
    • shell(gh:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3
    • git

    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 Container Maintainer loads about 1.1k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 534 words of instructions outside code blocks.

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

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). 534 words, ~1,140 tokens.

Download SKILL.mdSave it as .claude/skills/regression-container-maintainer/SKILL.md (or your agent's skills folder).
name
regression-container-maintainer
description
Use the published unified iccDEV container for maintainer smoke testing, pull request validation, issue reproduction, sanitizer review, and CI handoff.
allowed-tools
bash, read, grep, glob, shell(git:*), shell(docker:*), shell(gh:*)

Unified Container Maintainer

Use this skill for repeatable maintainer operations in ghcr.io/internationalcolorconsortium/iccdev.

Required Inputs

  1. Operation: basic smoke, PR validation, or issue reproduction.
  2. Image selector: choose latest, ci-qa-pr-docker-testing, ci-publish-colourbill-ctrl, a full-SHA tag, or a release tag at run time; do not embed a particular SHA as a reusable default.
  3. PR, issue, branch, or commit reference.
  4. Affected tool and smallest focused regression.
  5. Expected pass and failure signals.
  6. Host evidence directory.

Workflow

  1. Read ../../../docs/regression-container.md.
  2. Pull the selected tag, resolve it to a digest, record the digest and source revision, and execute the digest rather than the mutable tag.
  3. Mount only an evidence directory and start a disposable container.
  4. Require a clean initial Git worktree.
  5. For a PR, fetch pull/<number>/head and check out the ref detached.
  6. For an issue, reproduce with existing project tools and saved inputs.
  7. Rebuild the affected target, then run the focused regression and registered CTest wrapper.
  8. For local PR proof, pull the matching published integration image when validating ci-qa-pr-docker-testing or ci-publish-colourbill-ctrl; otherwise pull the selected published image. Record its resolved digest, mount the reviewed worktree read-only, and copy it to container-local scratch space. Run the local canonical-image build, reject compiler warnings, and run CTest excluding only the slow and calculator labels.
  9. When the PR-specific behavior is in an excluded suite, run its focused CTest wrapper in addition to the local container envelope.
  10. For AFL/CFL work, run iccdev-fuzz-env, record the patch-stack counts, and run the smallest matching smoke (iccdev-afl-smoke.sh --patches or .github/ci/cfl/build.sh --patches) before broader validation.
  11. Run broader CTest or GCC 15.2 strict parity only after the focused check passes.
  12. For coverage or profiling work, use a separate build tree and inventory lcov, genhtml, gcovr, llvm-cov, llvm-profdata, gprof, perf, strace, and the pinned $ICCDEV_FLAMEGRAPH_DIR. Run iccdev.profiling-smoke for ENABLE_PROFILING=ON builds. Treat unavailable hardware counters as environment evidence, not a correctness failure.
  13. Scan logs for compiler warnings, ASAN, UBSAN, and signal termination.
  14. Trigger ci-pr-action.yml explicitly for a pre-PR branch; a push alone does not trigger that workflow.
  15. Use only latest, ci-qa-pr-docker-testing, ci-publish-colourbill-ctrl, full-SHA, or release tags as selectors. Resolve the selector at run time; never hardcode one SHA tag as a long-lived workflow default. Existing legacy tags are continuity-only; do not introduce, recommend, or depend on other branch, run, or image-variant tags.
  16. Confirm the canonical image digest and hosted validation explicitly.
  17. Report exact image tag, digest, source revision, commands, results, evidence, and workflow URLs.
Show full SKILL.md (120 more words)Show less

For container/MCP runtime changes, run python3 .github/scripts/iccdev-container-smoke.py "$IMAGE" before dispatch. It checks real MCP and REST operations and requires native validation in the unified image. Keep stdin open through the last response and report the dynamic inventory. Use python3 -m pytest iccdev-mcp/tests -q for the focused scanner, entrypoint, server, and REST contracts; do not use CI as the first validation.

Safety Gates

  • Do not mount the Docker socket, SSH keys, or GitHub token into untrusted code.
  • Do not use custom C++ reproducers.
  • Do not use git clean to mask a dirty image.
  • Exit 1-127 is graceful; exit 128+ is signal termination.
  • Attribute sanitizer findings by stack-frame paths.
  • Preserve evidence outside the disposable container.

References

  • ../../../docs/regression-container.md
  • ../../../docs/regression-workflow-governance.md
  • ../../prompts/regression-container-maintainer.prompt.md
  • ../../instructions/build-system.instructions.md
  • ../../instructions/testing.instructions.md
  • ../../instructions/workflow-governance.instructions.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-container-maintainer of InternationalColorConsortium/iccDEV.

Open the folder on GitHubat commit 3c2425d

Compare with similar skills

Regression Container Maintainer 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 Container Maintainer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Regression Container Maintainer this skillInternationalColorConsortium/iccDEV183—~1.1kAutomated safety check: PassBSD-3-Clause
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands91k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    91k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    Auto-check passed

Categories

Questions about Regression Container Maintainer

What does Regression Container Maintainer do?

Use the published unified iccDEV container for maintainer smoke testing, pull request validation, issue reproduction, sanitizer review, and CI handoff. Regression Container Maintainer is an agent skill from InternationalColorConsortium/iccDEV. Use the published unified iccDEV container for maintainer smoke testing, pull request validation, issue reproduction, sanitizer review, and CI handoff.

When should I use Regression Container Maintainer?

Regression Container Maintainer fits situations like: tasks that involve Pull requests.

How do I install Regression Container Maintainer in Claude Code?

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

How do I install Regression Container Maintainer in Codex?

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

Can I use Regression Container Maintainer 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-container-maintainer -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-container-maintainer, .gemini/skills/regression-container-maintainer, .github/skills/regression-container-maintainer and .opencode/skills/regression-container-maintainer in your project.

What does Regression Container Maintainer need to run?

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

Does Regression Container Maintainer 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 Container Maintainer 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 Container Maintainer use?

Regression Container Maintainer 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 Container Maintainer use?

About 1.1k 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 Container Maintainer?

Skills that share tags, products or a category with Regression Container Maintainer: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 91k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Regression Container Maintainer?

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.