diff --git a/.agents/skills/openclaw-pr-maintainer/SKILL.md b/.agents/skills/openclaw-pr-maintainer/SKILL.md index 7bf881620b1..2fafe2885cb 100644 --- a/.agents/skills/openclaw-pr-maintainer/SKILL.md +++ b/.agents/skills/openclaw-pr-maintainer/SKILL.md @@ -45,6 +45,12 @@ gitcrawl cluster-detail openclaw/openclaw --id --member-limit 20 -- When asked for `X` issues or PRs to triage, `X` means qualified candidates, not sampled threads. +Triage is read/prove/patch-local by default. Do not commit unless Peter writes +`commit` in the current instruction for the exact diff being handled. Do not +treat earlier messages, inferred intent, "next", sweep momentum, or bundled +publish language as commit permission. If Peter asks for follow-up work without +saying `commit`, keep the files dirty after local fixes and proof. + Only list candidates that pass all gates: - small owner/surface, with a likely narrow fix and focused regression test diff --git a/.agents/skills/openclaw-small-bugfix-sweep/SKILL.md b/.agents/skills/openclaw-small-bugfix-sweep/SKILL.md index 67bb6d95de1..a9caf9105d8 100644 --- a/.agents/skills/openclaw-small-bugfix-sweep/SKILL.md +++ b/.agents/skills/openclaw-small-bugfix-sweep/SKILL.md @@ -13,8 +13,11 @@ Triage does not commit, push, create PRs, comment, close, label, land, or merge. Peter always wants to review code before commits. After local fixes and proof, stop with the diff summary, touched files, and test/gate output. -Do not commit, push, comment, close, label, land, merge, or otherwise publish until Peter explicitly says he has reviewed and approves that exact diff for that action. -If Peter asks for a bundled action like "commit push close", first confirm the code has already been reviewed in chat; if not, stop and ask for review/approval. +Do not commit unless Peter writes `commit` in the current instruction for the exact diff being handled. +Do not treat earlier messages, inferred intent, "next", sweep momentum, or bundled publish language as commit permission. +If Peter asks for follow-up work without saying `commit`, keep the files dirty after local fixes and proof. +Do not push, comment, close, label, land, merge, or otherwise publish until Peter explicitly asks for that exact action after the code has been reviewed. +If Peter asks for a bundled action like `commit push close`, first confirm the code has already been reviewed in chat; if not, stop with the dirty diff and ask for review/approval. ## Companion Skills @@ -55,7 +58,8 @@ Skip with terse reason. Do not pad with low-confidence fixes. - no drive-by refactors - tests near failing surface - docs only for changed public behavior -- no commit/push/create PR/comment/close/label/land/merge unless explicitly asked +- no commit unless Peter writes `commit` in the current instruction +- no push/create PR/comment/close/label/land/merge unless explicitly asked for that exact action after review ## PR Rules