Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

chapar-spack-repo-overlay

Estrelas3

Forks1

Atualizado13 de maio de 2026 às 21:29

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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

mmrezaie

mmrezaie/chapar

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Administradores de redes e sistemas de computadorInformática e Matemática·SOC 15-1244

SKILL.md

readonly

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.

Chapar Spack Repo Overlay

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.

Guardrails

Never edit the spack/ submodule.
Do not add or override recipes in spack_repo/ unless the user explicitly asks or an existing overlay package needs a targeted fix.
Prefer environment constraints in envs/<env> or persistent scope policy in etc/ when the problem is dependency selection rather than source behavior.
Keep patches narrow, platform/version-scoped, and documented with the upstream failure they address.
Do not vendor large source payloads or generated build artifacts.
Do not edit generated lock files or .spack-env/ directories.

Existing Overlay Packages

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.

Recipe Change Guidance

Keep package class names and directory names aligned with Spack naming rules.
Use existing Spack package APIs and style from nearby recipes.
Add version checks, variants, conflicts, and dependencies at the narrowest correct scope.
When adding a patch, include a short comment explaining the concrete build failure and condition it applies to.
Avoid pinning dependency minor or patch versions unless the user explicitly asks and the reason is documented.
For CUDA/GDR transport-related overlay work, also use chapar-cuda-gdr-transport.

Validation

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.

Mais deste repositório

mesmo repositório

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-config-scope-change

mmrezaie/chapar

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.

2026-06-103

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.

Chapar Spack Repo Overlay

Guardrails

Never edit the spack/ submodule.
Do not add or override recipes in spack_repo/ unless the user explicitly asks or an existing overlay package needs a targeted fix.
Prefer environment constraints in envs/<env> or persistent scope policy in etc/ when the problem is dependency selection rather than source behavior.
Keep patches narrow, platform/version-scoped, and documented with the upstream failure they address.
Do not vendor large source payloads or generated build artifacts.
Do not edit generated lock files or .spack-env/ directories.

Existing Overlay Packages

spack_repo/chapar_plus/packages/chapar_source_example/
spack_repo/chapar_plus/packages/chapar_binary_only_example/

Recipe Change Guidance

Keep package class names and directory names aligned with Spack naming rules.
Use existing Spack package APIs and style from nearby recipes.
Add version checks, variants, conflicts, and dependencies at the narrowest correct scope.
When adding a patch, include a short comment explaining the concrete build failure and condition it applies to.
Avoid pinning dependency minor or patch versions unless the user explicitly asks and the reason is documented.
For CUDA/GDR transport-related overlay work, also use chapar-cuda-gdr-transport.

Validation

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.