菜单
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.
用 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'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.
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-buildcache |
| description | 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. |
Use this playbook for ${CHAPAR_BUILDCACHE_ROOT}/<os>,
${CHAPAR_CCACHE_ROOT}/<os>, and cache logic used by Chapar Spack environments.
The current release-helper implementation is hpcsim-specific, but the cache
policy is project-wide and should remain usable by future environments.
envs/hpcsim/release.sh migrate-buildcache for hpcsim.INSTALL_TREE_PADDED_LENGTH and
BUILDCACHE_LAYOUT_VERSION where those helpers are used.envs/hpcsim/hpcsim-site.env, not tracked YAML.docs/buildcache.md
envs/hpcsim/release.sh # current hpcsim release/cache helper
ci/push-buildcache.sh
.github/workflows/incus-spack-build.yml
etc/system/rocky9/mirrors.yaml
etc/system/rocky10/mirrors.yaml
envs/hpcsim/hpcsim-site.env.example
For future environments, inspect their workflow/build helper before assuming the hpcsim paths or variable names apply.
source ./etc/init.sh
ENV_PATH=envs/hpcsim # or envs/<future-env>
spack mirror list
spack config blame mirrors
spack -e "${ENV_PATH}" config blame mirrors
For hpcsim release-helper cache status:
OS_NAME=rocky9 bash envs/hpcsim/release.sh status
A cache with payloads but no index is invisible to Spack reuse. Build helpers should refresh indexes before concretization when needed.
Do not run destructive cache cleanup. If cleanup is requested, require explicit confirmation and document what will be removed.
bash -n envs/hpcsim/release.sh
bash -n ci/push-buildcache.sh
git diff --check
If the change targets a future environment helper, validate that helper with
bash -n as well.
If documentation is updated with behavior changes, keep docs in the same commit
only when they explain the behavior change; otherwise split commits with
chapar-commit.