メニュー
Modify or review Chapar local Spack package overlay recipes and patches under spack_repo/chapar_plus. Use only when the user explicitly asks for local package recipe work, binary-only package examples, source package examples, or package overlay debugging.
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.
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.
| name | chapar-spack-repo-overlay |
| description | Modify or review Chapar local Spack package overlay recipes and patches under spack_repo/chapar_plus. Use only when the user explicitly asks for local package recipe work, binary-only package examples, source package examples, or package overlay debugging. |
Use this playbook for local Spack package overlay work under spack_repo/chapar_plus.
Most environment/package policy changes belong under envs/ or etc/; use this
skill only when a local recipe or patch is actually required.
spack/ submodule.spack_repo/ unless the user explicitly asks
or an existing overlay package needs a targeted fix.envs/<env> or persistent scope policy in
etc/ when the problem is dependency selection rather than source behavior..spack-env/ directories.spack_repo/chapar_plus/packages/chapar_source_example/
spack_repo/chapar_plus/packages/chapar_binary_only_example/
These are teaching examples for industrial simulation packaging. Keep them small and easy to read; they should demonstrate source-available and binary-only packaging patterns without vendoring real proprietary payloads.
chapar-cuda-gdr-transport.python3 -m py_compile spack_repo/chapar_plus/packages/<package>/package.py
source ./etc/init.sh
spack spec <package>
git diff --check -- spack_repo/chapar_plus
If the overlay change is platform-specific and local validation is on a different platform, state which CI or runner is needed for full validation.