name: clownfish-cloud-pr

description: Use when launching Clownfish in GitHub Actions to create or update one guarded GitHub implementation PR from issue/PR refs, a ClawSweeper report, or a custom maintainer prompt.

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

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.

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. Keep `CLOWNFISH_ALLOW_MERGE=0` unless Peter

explicitly opens the merge gate.

- One cluster, one branch, one PR: `clownfish/<cluster-id>`.

- No security-sensitive work.

- Do not close duplicates before the fix PR path exists, lands, or is proven

unnecessary.

- Codex workers do not get GitHub tokens; deterministic scripts own writes.