원클릭으로 Manus에서 모든 스킬 실행

regression-container-maintainer

스타165

포크47

업데이트2026년 7월 21일 19:21

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

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

InternationalColorConsortium

InternationalColorConsortium/iccDEV

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Regression Container Maintainer

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

Required Inputs

Operation: basic smoke, PR validation, or issue reproduction.
Image tag: latest for initial interactive work or an immutable SHA tag for reproducible validation.
PR, issue, branch, or commit reference.
Affected tool and smallest focused regression.
Expected pass and failure signals.
Host evidence directory.

Workflow

Read ../../../docs/regression-container.md.
Pull the image and record its digest and source revision. For latest, verify both values before using the image.
Mount only an evidence directory and start a disposable container.
Require a clean initial Git worktree.
For a PR, fetch pull/<number>/head and check out the ref detached.
For an issue, reproduce with existing project tools and saved inputs.
Rebuild the affected target, then run the focused regression and registered CTest wrapper.
Run broader CTest or GCC strict parity only after the focused check passes.
Scan logs for compiler warnings, ASAN, UBSAN, and signal termination.
Trigger ci-pr-action.yml explicitly for a pre-PR branch; a push alone does not trigger that workflow.
Compare all Dockerfile* files between ci-qa-pr-docker-testing and ci-qa-flags; carry every applicable container fix to both branches.
Confirm the ci-qa-flags branch update and hosted validation explicitly.
Promote the verified immutable digest to latest only after all image smoke tests and regression CTest checks succeed: automatically from master, or explicitly from the protected Docker-testing branch with publish-regression-latest=true. Never promote it from other branches.
Report exact image tag, digest, source revision, commands, results, evidence, and workflow URLs.

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

이 저장소의 다른 Skills

같은 저장소

maintainer-ci-ctest

InternationalColorConsortium/iccDEV

Maintainer workflow for scoping and updating iccDEV CI, CTest, CPack, sanitizer, workflow, and release-gate infrastructure.

2026-07-21165

pre-pr-security-cycle

InternationalColorConsortium/iccDEV

Maintainer workflow for the pre-PR secure loop: code, build/test, SAST/CodeQL, dynamic sanitizer checks, fixes, and concise handoff.

2026-07-08165

maintainer-label-system

InternationalColorConsortium/iccDEV

Maintain iccDEV repository labels, path labeler rules, issue triage labels, PR CI status labels, and label workflow governance.

2026-07-07165

sanitizer-repro

InternationalColorConsortium/iccDEV

Reproduce and triage ASAN/UBSAN findings against iccDEV tools with authoritative exit-code and stack-frame handling.

2026-05-28165

regression-workflow-governance

InternationalColorConsortium/iccDEV

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

2026-05-22165

vcpkg-export-consumer-debug

InternationalColorConsortium/iccDEV

Debug iccDEV vcpkg, install/export, uninstall, and packaged consumer failures, especially Windows static CRT and path quoting regressions.

2026-05-12165

name	regression-container-maintainer
description	Use the published iccDEV regression 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:*)"]

Regression Container Maintainer

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

Required Inputs

Operation: basic smoke, PR validation, or issue reproduction.
Image tag: latest for initial interactive work or an immutable SHA tag for reproducible validation.
PR, issue, branch, or commit reference.
Affected tool and smallest focused regression.
Expected pass and failure signals.
Host evidence directory.

Workflow

Read ../../../docs/regression-container.md.
Pull the image and record its digest and source revision. For latest, verify both values before using the image.
Mount only an evidence directory and start a disposable container.
Require a clean initial Git worktree.
For a PR, fetch pull/<number>/head and check out the ref detached.
For an issue, reproduce with existing project tools and saved inputs.
Rebuild the affected target, then run the focused regression and registered CTest wrapper.
Run broader CTest or GCC strict parity only after the focused check passes.
Scan logs for compiler warnings, ASAN, UBSAN, and signal termination.
Trigger ci-pr-action.yml explicitly for a pre-PR branch; a push alone does not trigger that workflow.
Compare all Dockerfile* files between ci-qa-pr-docker-testing and ci-qa-flags; carry every applicable container fix to both branches.
Confirm the ci-qa-flags branch update and hosted validation explicitly.
Promote the verified immutable digest to latest only after all image smoke tests and regression CTest checks succeed: automatically from master, or explicitly from the protected Docker-testing branch with publish-regression-latest=true. Never promote it from other branches.
Report exact image tag, digest, source revision, commands, results, evidence, and workflow URLs.

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