ワンクリックでManusで任意のスキルを実行

chapar-config-scope-change

スター3

フォーク1

更新日2026年6月10日 16:06

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 ページを確認してインストールできます。

Manusで実行

ソース

mmrezaie

mmrezaie/chapar

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Chapar Config Scope Change

Use this playbook when editing persistent Spack scopes under etc/.

Scope Hierarchy

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

Rules

Model only expected externals: OS/bootstrap compilers, glibc on Rocky, unavoidable platform runtime pieces, ccache where enabled.
Do not model ordinary link-time libraries (OpenSSL, zlib, libpng, curl, OpenBLAS, HDF5, NetCDF) as OS externals unless explicitly justified with matching dev metadata.
CUDA should be built by Spack for hpcsim GPU packages, not modeled as a host external.
Do not add OS Intel oneAPI compiler/MPI RPMs or GitHub CLI RPMs to hpcsim Rocky builder bootstrap policy. Use Spack for Intel MPI and any future Intel compiler dependency unless the user explicitly changes that policy.
OS-specific overrides use include.yaml with when: conditionals.
Keep paths per-platform; do not mix Rocky 9/Rocky 10 stores or caches.
Site-specific release, buildcache, ccache, group, and public root paths belong in ignored envs/hpcsim/hpcsim-site.env, not tracked YAML.

Inspection

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

Editing Procedure

Decide if the change is system, user, or environment policy.
Decide if it is shared or OS-specific.
Edit the narrowest appropriate YAML file.
Preserve existing YAML style: 2-space indentation, sorted sections where practical.
Validate with config blame and hpcsim concretization when relevant.

Validation

source ./etc/init.sh
spack config scopes -p
spack config blame packages
spack -e envs/hpcsim concretize -f
git diff --check

このリポジトリの他の Skills

同じリポジトリ

chapar-ci-artifact-watch

mmrezaie/chapar

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.

2026-06-113

chapar-incus-ci-triage

mmrezaie/chapar

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.

2026-06-113

chapar-release-helper

mmrezaie/chapar

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.

2026-06-113

chapar-buildcache

mmrezaie/chapar

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.

2026-06-103

chapar-commit

mmrezaie/chapar

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.

2026-06-103

chapar-cuda-gdr-transport

mmrezaie/chapar

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.

2026-06-103

Chapar Config Scope Change

Use this playbook when editing persistent Spack scopes under etc/.

Scope Hierarchy

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

Rules

Model only expected externals: OS/bootstrap compilers, glibc on Rocky, unavoidable platform runtime pieces, ccache where enabled.

Do not model ordinary link-time libraries (OpenSSL, zlib, libpng, curl, OpenBLAS, HDF5, NetCDF) as OS externals unless explicitly justified with matching dev metadata.

CUDA should be built by Spack for hpcsim GPU packages, not modeled as a host external.

Do not add OS Intel oneAPI compiler/MPI RPMs or GitHub CLI RPMs to hpcsim Rocky builder bootstrap policy. Use Spack for Intel MPI and any future Intel compiler dependency unless the user explicitly changes that policy.

OS-specific overrides use include.yaml with when: conditionals.

Keep paths per-platform; do not mix Rocky 9/Rocky 10 stores or caches.

Site-specific release, buildcache, ccache, group, and public root paths belong in ignored envs/hpcsim/hpcsim-site.env, not tracked YAML.

Inspection

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

Editing Procedure

Decide if the change is system, user, or environment policy.

Decide if it is shared or OS-specific.

Edit the narrowest appropriate YAML file.

Preserve existing YAML style: 2-space indentation, sorted sections where practical.

Validate with config blame and hpcsim concretization when relevant.

Validation

source ./etc/init.sh spack config scopes -p spack config blame packages spack -e envs/hpcsim concretize -f git diff --check

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.