@@ -7,17 +7,19 @@ description: Fix only small, high-certainty OpenClaw bugs from a pasted issue/PR
7788Batch workflow for pasted OpenClaw issue/PR refs.
99Execute, do not summarize.
10-Triage does not commit, push, create PRs, comment, close, label, land, or merge.
10+Triage reviews, proves, and patches local fixes first; publishing waits for Peter's manual review.
11111212## Peter Review Gate
13131414Peter always wants to review code before commits.
15-After local fixes and proof, stop with the diff summary, touched files, and test/gate output.
16-Do not commit unless Peter writes `commit` in the current instruction for the exact diff being handled.
17-Do not treat earlier messages, inferred intent, "next", sweep momentum, or bundled publish language as commit permission.
18-If Peter asks for follow-up work without saying `commit`, keep the files dirty after local fixes and proof.
19-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.
20-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.
15+Default flow:
16+1. Review each issue deeply enough to prove current behavior and root cause.
17+2. Fix only easy, high-confidence bugs with narrow ownership and focused proof.
18+3. Stop with the dirty diff summary, touched files, and test/gate output for Peter's manual review.
19+4. After Peter approves shipping, make one commit per accepted fix, with a changelog entry for each user-facing fix.
20+5. Pull/rebase, push, then comment and close only the fixed or explicitly triaged-closed issues.
21+22+Do not batch unrelated issue fixes into one commit. Do not push, create PRs, comment, close, label, land, merge, or otherwise publish during the review/prove phase.
21232224## Companion Skills
2325@@ -58,8 +60,9 @@ Skip with terse reason. Do not pad with low-confidence fixes.
5860- no drive-by refactors
5961- tests near failing surface
6062- docs only for changed public behavior
61-- no commit unless Peter writes `commit` in the current instruction
62-- no push/create PR/comment/close/label/land/merge unless explicitly asked for that exact action after review
63+- no commit during the review/prove phase
64+- after Peter approves shipping, one commit plus changelog per accepted user-facing fix
65+- no push/create PR/comment/close/label/land/merge until Peter approves shipping after review
63666467## PR Rules
6568此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。