菜单
Resume MOAT. Detect this host's AMD platform, find the next actionable project, and dispatch the right role. Use when starting work in the MOAT repo or when asked to continue porting or "port next".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/AMD-Ecosystem/moat --skill port-next命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Check what MOAT needs from a person -- ports approved and ready to submit upstream, maintainers waiting on a reply, upstream PRs that merged or closed, and landed work going stale. Use at the start of a session, after approving a port, when a maintainer comments, or when the user asks what needs attention.
Port a CUDA project to ROCm/HIP for AMD GPUs. Strategy selection, the AMD-strict-where-CUDA-is-lenient fault classes, wavefront-size portability, library substitutions, and the validation bar. Use when planning, implementing, reviewing or validating a CUDA-to-HIP port, or when a HIP build compiles but misbehaves at runtime.
Port a CUDA project to ROCm/HIP for AMD GPUs. Strategy selection, the AMD-strict-where-CUDA-is-lenient fault classes, wavefront-size portability, library substitutions, and the validation bar. Use when planning, implementing, reviewing or validating a CUDA-to-HIP port, or when a HIP build compiles but misbehaves at runtime.
基于 SOC 职业分类
正在显示 SKILL.md
| name | port-next |
| description | Resume MOAT. Detect this host's AMD platform, find the next actionable project, and dispatch the right role. Use when starting work in the MOAT repo or when asked to continue porting or "port next". |
Run the MOAT pipeline for the next available project on this host.
port/<name> in this repo, not on main -- orient refuses the trunk. An in-flight project's folder lives only on its own branch, so check out the branch for the project you intend to work (git checkout port/<name>), or create it when adopting one. Not to be confused with moat-port, which is the branch on the FORK that holds the code. If nothing is actionable here, python3 utils/moatlib.py fleet <platform> names work on other branches.bash utils/orient.sh. It pulls the latest state, detects the AMD arch, and prints the next project, its state, and the stage (intake / planner / porter / reviewer / validator), or NONE..claude/agents/; Codex discovers the matching adapters in .codex/agents/; both execute the canonical role body in .claude/agents/<stage>.md. Stages are intake, planner, porter, reviewer and validator. Nothing after approval is a stage: submitting upstream and the maintainer rounds that follow are the moat-checkup skill, run in this session, because each step ends at a person. The child agent reads AGENTS.md (Pipeline, Human decisions and external writes, Standing rules, Stop discipline), plan.md, notes.md, and the cuda-to-rocm skill.blocked, ask a specific question).