vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 13:10:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: require explicit commit instruction in triage skills

Browse Source
This commit is contained in:
Peter Steinberger
2026-05-02 02:43:45 +01:00
parent 7987fac21a
commit c851a58518
2 changed files with 13 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.agents/skills/openclaw-pr-maintainer/SKILL.md
View File

@@ -45,6 +45,12 @@ gitcrawl cluster-detail openclaw/openclaw --id <cluster-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

10
.agents/skills/openclaw-small-bugfix-sweep/SKILL.md
View File

@@ -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