docs: document Clownfish comment commands · openclaw/openclaw@38e5697
steipete
·
2026-04-29
·
via Recent Commits to openclaw:main
File tree
.agents/skills/clownfish-cloud-pr
| Original file line number | Diff line number | Diff line change |
|---|
@@ -49,6 +49,37 @@ Do not use `--dispatch` until the job is committed and pushed; the workflow
|
49 | 49 | reads the job path from GitHub. Keep `CLOWNFISH_ALLOW_MERGE=0` unless Peter |
50 | 50 | explicitly opens the merge gate. |
51 | 51 | |
| 52 | +## Maintainer Comment Commands |
| 53 | + |
| 54 | +Clownfish can also be asked from target repo comments, but only by maintainers. |
| 55 | +Use `/clownfish ...` or `@openclaw-clownfish ...`; do not use `@clownfish` |
| 56 | +because that is a separate GitHub user. |
| 57 | + |
| 58 | +Supported commands: |
| 59 | + |
| 60 | +```text |
| 61 | +/clownfish status |
| 62 | +/clownfish fix ci |
| 63 | +/clownfish address review |
| 64 | +/clownfish rebase |
| 65 | +/clownfish explain |
| 66 | +/clownfish stop |
| 67 | +@openclaw-clownfish fix ci |
| 68 | +``` |
| 69 | + |
| 70 | +The router accepts `OWNER`, `MEMBER`, and `COLLABORATOR` comments by default. |
| 71 | +Contributor comments are ignored without a reply. Repair commands dispatch |
| 72 | +`cluster-worker.yml` only for existing Clownfish PRs with the `clownfish` label |
| 73 | +or `clownfish/*` branch. |
| 74 | + |
| 75 | +```bash |
| 76 | +npm run comment-router -- --repo openclaw/openclaw --lookback-minutes 180 |
| 77 | +npm run comment-router -- --repo openclaw/openclaw --execute --wait-for-capacity |
| 78 | +``` |
| 79 | + |
| 80 | +Scheduled routing stays dry until `CLOWNFISH_COMMENT_ROUTER_EXECUTE=1` is set in |
| 81 | +`openclaw/clownfish` repo variables. |
| 82 | + |
52 | 83 | ## Guardrails |
53 | 84 | |
54 | 85 | - One cluster, one branch, one PR: `clownfish/<cluster-id>`. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
