菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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.
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.
基于 SOC 职业分类
| name | chapar-commit |
| description | 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. |
Use this playbook before any Chapar commit or push.
git status --short
git diff --stat
git diff
git log --oneline -8 --decorate
If the branch is not what the user intended, stop and ask or switch only if explicitly requested.
Create separate commits for separate review contexts:
Do not mix documentation/comment-only changes with behavior/config/CI changes unless inseparable. If inseparable, explain why in the commit body.
Use a short subject plus a body that explains:
Avoid messages that only restate the diff.
Example:
Add Rocky 10 hpcsim release support
The hpcsim environment now targets Rocky 9 and Rocky 10 with one Spack-built GCC 15 compiler stack. Keeping the package policy in one manifest avoids review drift across per-OS directories while release-time scopes continue to isolate stores and module trees by OS.
The site-local roots and shared cache paths are loaded from ignored envs/hpcsim/hpcsim-site.env so cluster-specific mount points do not leak into tracked config.
Validation: bash -n envs/hpcsim/release.sh; git diff --check ...
main.[skip ci] only when intentionally avoiding push-triggered workflows.main push.git status --short
git log --oneline -3