菜单
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.
用 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.
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.
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-config-scope-change |
| description | 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. |
Use this playbook when editing persistent Spack scopes under etc/.
Chapar follows normal Spack precedence:
defaults > system > site > user > spack > environment > command line
Chapar uses:
etc/system/base/ # shared machine/site policy
etc/system/{rocky9,rocky10} # OS-specific system externals/policy
etc/user/base/ # shared user policy
etc/user/{rocky9,rocky10} # OS-specific user paths/modules/cache
envs/hpcsim/ # environment-level hpcsim roots/policy
OS routing is controlled by:
etc/system/include.yaml
etc/user/include.yaml
envs/hpcsim/spack.yaml
include.yaml with when: conditionals.envs/hpcsim/hpcsim-site.env, not tracked YAML.source ./etc/init.sh
spack config scopes -p
spack arch
spack config blame packages
spack config blame config
spack config blame mirrors
spack config blame modules
source ./etc/init.sh
spack config scopes -p
spack config blame packages
spack -e envs/hpcsim concretize -f
git diff --check