菜单
Modify or debug Chapar's current hpcsim release helper envs/hpcsim/release.sh. Use for hpcsim release builds, staging/promote logic, module refresh, generated Spack scopes, and release metadata. For generic package/env edits, use chapar-spack-env-change.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Inspect live Chapar CI/CD build progress by reading durable filesystem artifact roots directly instead of waiting for GitHub Actions or GitLab UI logs. Use whenever the user asks what is happening with a running, queued, stuck, timed-out, or slow CI build, especially Rocky 9/Rocky 10 hpcsim builds, package installs, modulefile publication, release roots, buildcache roots, ccache roots, or site-specific mounts such as /resources, /Volumes/resources, ~/resources, or another mounted artifact tree.
Triage Chapar GitHub Actions Incus Spack-environment CI failures, including hpcsim Rocky 9/Rocky 10 builds and future environment workflows. Use when an Incus Spack build fails, succeeds on one Rocky version but not the other, or when inspecting self-hosted runner/build logs.
Modify or debug Chapar buildcache or shared ccache behavior, migration, quarantine, index refresh, and cache publication for hpcsim or future Spack environments. Use for docs/buildcache.md, ci/push-buildcache.sh, release helper migration, or buildcache CI failures.
Prepare Chapar commits and pushes with the project's commit-splitting and message policy. Use whenever the user asks to commit, push, split commits, or prepare a PR branch.
Modify Chapar Spack configuration scopes under etc/system, etc/user, include.yaml, externals, mirrors, providers, modules, or install-tree settings. Use for config layering and OS-specific scope changes.
Handle Chapar CUDA/GDR-capable transport issues in GPU-enabled Spack environments, especially hpcsim. Use when build failures involve CUDA-aware MPI, GPUDirect, UCX, Open MPI, libfabric, GDRCopy, NCCL, or NVSHMEM.
| name | chapar-release-helper |
| description | Modify or debug Chapar's current hpcsim release helper envs/hpcsim/release.sh. Use for hpcsim release builds, staging/promote logic, module refresh, generated Spack scopes, and release metadata. For generic package/env edits, use chapar-spack-env-change. |
Use this playbook before editing envs/hpcsim/release.sh. This skill is
intentionally hpcsim-specific because that is the release helper that exists
today. If a future environment gets its own release helper, copy the invariants
that apply but inspect that helper's own paths and variables first.
releases/.<release-id>.staging.<pid>.releases/<release-id>
after install, module generation, and manifest writing succeed.current symlink atomically and may also update
configured shared module-root symlinks per architecture.{name}/{version}.make_scope controls release-only:
Do not move release-only policy into persistent system/user scopes unless the user explicitly requests a persistent behavior change.
Always run:
bash -n envs/hpcsim/release.sh
git diff --check -- envs/hpcsim/release.sh
For non-destructive path/status checks:
OS_NAME=rocky9 bash envs/hpcsim/release.sh status
Do not run build/promote commands unless explicitly asked.
If changing cache layout, migration, index refresh, autopush, or quarantine
behavior, use chapar-buildcache too.
If changing install_cuda_libfabric_specs, CUDA target/stub handling, UCX, Open
MPI, or libfabric behavior, use chapar-cuda-gdr-transport too.