菜单
Maintain Chapar OpenCode configuration, agent skill layout, project skill migration, permission rules, AGENTS.md, and agents/skills playbooks. Use when changing opencode.json, creating or moving project skills, updating skill trigger policy, or removing legacy Pi skill references.
用 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-opencode-skills |
| description | Maintain Chapar OpenCode configuration, agent skill layout, project skill migration, permission rules, AGENTS.md, and agents/skills playbooks. Use when changing opencode.json, creating or moving project skills, updating skill trigger policy, or removing legacy Pi skill references. |
Use this playbook when editing OpenCode-facing agent configuration or the
project-local skill catalog under agents/skills.
Key files:
opencode.json
AGENTS.md
agents/README.md
agents/skills/*/SKILL.md
Use skill-creator too when creating or substantially rewriting a skill.
agents/skills.AGENTS.md as baseline repository guidance; keep detailed workflow logic
in focused skills.opencode.json permissions narrow and task-oriented. Do not add broad
write, shell, token, or secret access just to make a workflow convenient.spack/, .spack-env/, lockfiles, or .git/.agents/skills/<name>/SKILL.md with kebab-case name
and a description that states when to use it.AGENTS.md when the skill covers a repository workflow that agents
must consult before changing files.agents/README.md when the catalog structure or major skill set
changes.opencode.json only for paths and commands the skills actually need.python3 agents/skills/skill-creator/scripts/quick_validate.py agents/skills/<skill-name>
git diff --check
Search for stale paths before finishing:
rg 'legacy Pi|pi/skills' AGENTS.md agents opencode.json .gitignore
If historical Pi references remain only in external upstream links, call that out explicitly.