$ loading_
帮助团队在 GitHub Actions 中创建或更新受保护的实现 PR 并支持自动合并审查流程。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "clownfish-cloud-pr" 技能： 1. 下载 https://raw.githubusercontent.com/openclaw/clownfish/main/.agents/skills/clownfish-cloud-pr/SKILL.md 2. 保存为 ~/.claude/skills/clownfish-cloud-pr/SKILL.md 3. 装好后重载技能，告诉我可以用了
请在 GitHub Actions 中启动 clownfish-cloud-pr，基于 issue #128 创建一个受保护的实现 PR，并使用默认审查流程。
生成一个关联该问题单的受保护实现 PR，并进入既定审查流程。
请使用 clownfish-cloud-pr，基于 PR #56 和最新的 ClawSweeper 报告更新现有实现 PR，并保留受保护设置。
现有实现 PR 被更新，内容反映最新报告结果且继续保持受保护状态。
请将 PR #73 通过 clownfish-cloud-pr 纳入经过 ClawSweeper 审查的 Clownfish 自动合并流程，并附加维护者提示“优先处理测试失败项”。
该 PR 被加入受审查的自动合并流程，并带有维护者指定的处理指引。
Use this skill when the user wants Codex to ask Clownfish to create a PR in the cloud from issue/PR refs plus a custom prompt.
cd ~/Projects/clownfish
git status --short --branch
gh variable list --repo openclaw/clownfish --json name,value \
--jq 'map(select(.name|test("^CLOWNFISH_"))) | sort_by(.name) | .[] | {name,value}'
Keep merge gated unless Peter explicitly opens it. Execute/fix gates are closed
unless the repo variables are literally 1; normal fix-PR work needs an
intentional execution window:
gh variable set CLOWNFISH_ALLOW_EXECUTE --repo openclaw/clownfish --body 1
gh variable set CLOWNFISH_ALLOW_FIX_PR --repo openclaw/clownfish --body 1
gh variable set CLOWNFISH_ALLOW_MERGE --repo openclaw/clownfish --body 0
gh variable set CLOWNFISH_ALLOW_AUTOMERGE --repo openclaw/clownfish --body 0
Reset CLOWNFISH_ALLOW_EXECUTE=0 and CLOWNFISH_ALLOW_FIX_PR=0 after the
window. If those vars are absent or not 1, execute/autonomous workflow runs
stay plan-only/no-mutation.
From refs and a custom prompt:
npm run create-job -- \
--repo openclaw/openclaw \
--refs 123,456 \
--prompt-file /tmp/clownfish-prompt.md
From a ClawSweeper report:
npm run create-job -- \
--from-report ../clawsweeper/records/openclaw-openclaw/items/123.md
The script checks for an existing open PR/body match and remote branch named
clownfish/<cluster-id> before writing a duplicate job. Use --dry-run to
inspect the exact job body and --force only after deciding the duplicate check
is stale.
The skill can trigger replacement PR writing through the normal create-job
and dispatch path. Put the maintainer decision in the prompt:
Treat #123 as useful source work. If the source branch cannot be safely updated
because it is uneditable, stale, draft-only, unmergeable, or unsafe, create a
narrow Clownfish replacement PR instead of waiting. Preserve the source PR
author as co-author, credit the source PR in the replacement PR body, and close
only that source PR after the replacement PR is opened.
The worker should emit repair_strategy=replace_uneditable_branch and list the
source PR URL in source_prs. The deterministic executor opens or updates
clownfish/<cluster-id>, adds non-bot source PR authors as Co-authored-by
trailers, and closes the superseded source PR only after the replacement PR
exists. New replacement PRs are blocked when the touched area already has
CLOWNFISH_MAX_ACTIVE_PRS_PER_AREA open Clownfish PRs.
npm run validate:job -- jobs/openclaw/inbox/clawsweeper-openclaw-openclaw-123.md
npm run render -- jobs/openclaw/inbox/clawsweeper-openclaw-openclaw-123.md --mode autonomous >/tmp/clownfish-rendered-prompt.md
git add jobs/openclaw/inbox/clawsweeper-openclaw-openclaw-123.md
git commit -m "chore: add ClawSweeper promoted job"
git push origin main
npm run dispatch -- jobs/openclaw/inbox/clawsweeper-openclaw-openclaw-123.md \
--mode autonomous \
--runner blacksmith-4vcpu-ubuntu-2404 \
--execution-runner blacksmith-16vcpu-ubuntu-2404 \
--model gpt-5.5
Do not use --dispatch until the job is committed and pushed; the workflow
reads the job path from GitHub.
Clownfish can also be asked from target repo comments, but only by maintainers.
Use /clownfish ... or @openclaw-clownfish ...; do not use @clownfish
because that is a separate GitHub user.
Supported commands:
/clownfish status
/clownfish fix ci
/clownfish address review
/clownfish rebase
/clownfish automerge
/clownfish explain
/clownfish stop
@openclaw-clownfish fix ci
The router accepts OWNER, MEMBER, and COLLABORATOR comments by default.
Contributor comments are ignored without a reply. Repair commands dispatch
cluster-worker.yml for existing Clownfish PRs and for PRs explicitly opted
into clownfish:automerge.
…