Back to Details

openclaw-small-bugfix-sweep

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

OpenClaw Small Bugfix Sweep

OpenClaw小漏洞修复扫描

Batch workflow for pasted OpenClaw issue/PR refs. Execute, do not summarize. Triage does not commit, push, create PRs, comment, close, label, land, or merge.
针对粘贴的OpenClaw问题/PR引用的批量处理流程。 直接执行，不要总结。 分类阶段不进行提交、推送、创建PR、评论、关闭、打标签、落地或合并操作。

Peter Review Gate

Peter审查关卡

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 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.
Peter要求在提交代码前必须进行审查。 完成本地修复并验证后，仅输出差异摘要、修改的文件以及测试/关卡结果即可停止操作。 只有当Peter在当前指令中针对正在处理的具体差异明确写下
commit
时，才能进行提交。 不得将早期消息、推断的意图、"下一步"、扫描推进节奏或捆绑发布的表述视为提交许可。 如果Peter要求后续工作但未提及
commit
，则在完成本地修复和验证后保持文件处于未提交状态。 在代码经过审查且Peter明确要求执行具体操作之前，不得进行推送、评论、关闭、打标签、落地、合并或其他任何发布操作。 如果Peter要求执行如
commit push close
这类捆绑操作，首先要确认代码已在聊天中完成审查；若未审查，则保留未提交的差异并请求审查/批准。

Companion Skills

配套技能

Use 
$gitcrawl
first, 
$openclaw-pr-maintainer
for live GitHub hygiene, 
$github-deep-review
posture for source tracing, and 
$openclaw-testing
for proof.
首先使用
$gitcrawl
，
$openclaw-pr-maintainer
用于实时GitHub维护，
$github-deep-review
用于源码追踪，
$openclaw-testing
用于验证。

Loop

循环流程

For each ref:
  1. Read live target with 
    gh
    .
  2. Check 
    gitcrawl
    for related, duplicate, closed, or already-fixed threads.
  3. Read body, comments, linked refs, changed files, current code, adjacent tests, and dependency contracts when relevant.
  4. Trace the real runtime path.
  5. For issues: fix locally only if this is a bug, current code proves root cause, the implicated path is clear, and a narrow patch is cleaner than refactor.
  6. For PRs: decide 
    ready-to-merge
    , 
    needs-fixup
    , or 
    skip
    ; do not alter PR branches unless explicitly asked.
  7. Add focused regression proof when practical for local issue fixes or PR readiness checks.
  8. Run the smallest meaningful gate.
  9. Continue until every pasted ref is fixed or classified.
No subagents unless explicitly requested.
针对每个引用：
  1. 使用
    gh
    读取实时目标内容。
  2. 通过
    gitcrawl
    检查相关、重复、已关闭或已修复的线程。
  3. 阅读内容主体、评论、关联引用、修改的文件、当前代码、相关测试以及相关的依赖协议。
  4. 追踪实际运行路径。
  5. 对于问题：仅当确定是漏洞、当前代码能证明根本原因、涉及路径清晰且窄补丁比重构更简洁时，才进行本地修复。
  6. 对于PR：判断为
    ready-to-merge
    （可合并）、
    needs-fixup
    （需修正）或
    skip
    （跳过）；除非明确要求，否则不得修改PR分支。
  7. 在可行的情况下，为本地问题修复或PR就绪检查添加针对性的回归验证。
  8. 运行最小且有意义的关卡测试。
  9. 持续执行，直到所有粘贴的引用都被修复或分类完成。
除非明确要求，否则不使用子Agent。

Skip If

跳过条件

  • not a bug
  • config/docs/workflow/release/support/dependency/product work
  • repro or root cause is uncertain
  • larger refactor or owner-boundary change is cleaner
  • already fixed on current 
    main
  • dependency behavior is guessed
  • no focused proof is feasible
Skip with terse reason. Do not pad with low-confidence fixes.
  • 不是漏洞
  • 属于配置/文档/工作流/发布/支持/依赖/产品相关工作
  • 复现步骤或根本原因不确定
  • 较大的重构或跨所有者边界的修改更合适
  • 当前
    main
    分支上已修复
  • 依赖行为仅为猜测
  • 无法进行针对性验证
跳过需给出简洁理由。不得添加低可信度的修复内容。

Fix Rules

修复规则

  • owner module first; generic seam only when required
  • existing patterns/helpers/types
  • no drive-by refactors
  • tests near failing surface
  • docs only for changed public behavior
  • 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
  • 优先修复所有者模块；仅在必要时使用通用接口
  • 遵循现有模式/辅助工具/类型
  • 不得顺便进行重构
  • 测试需靠近问题出现的代码区域
  • 仅当公共行为发生变化时才更新文档
  • 只有当Peter在当前指令中写下
    commit
    时才能提交
  • 在审查后未明确要求执行具体操作时，不得进行推送/创建PR/评论/关闭/打标签/落地/合并

PR Rules

PR规则

  • ready-to-merge
    : code is good, current head checked, required proof is green or clearly pending only external CI; list for maintainer merge or 
    @clawsweeper automerge
  • needs-fixup
    : small bug is clear, but PR branch needs changes; list exact files/tests and wait for explicit fix/push/automerge instruction
  • skip
    : broad, stale, speculative, config/product/security/release, owner-boundary, or refactor-sized
  • if source PR is untrusted/uneditable, do not create a replacement PR during sweep
  • ready-to-merge
    （可合并）：代码质量良好，已检查当前最新版本，必要验证已通过或仅等待外部CI；列出供维护者合并或使用
    @clawsweeper automerge
    自动合并
  • needs-fixup
    （需修正）：存在明确的小漏洞，但PR分支需要修改；列出具体文件/测试并等待明确的修复/推送/自动合并指令
  • skip
    （跳过）：范围过广、已过时、推测性的，或属于配置/产品/安全/发布、跨所有者边界、重构级别的内容
  • 若源PR不可信/不可编辑，扫描期间不得创建替代PR

Output Shape

输出格式

Ledger: 
fixed-local
, 
ready-to-merge
, 
needs-fixup
, 
skipped
, 
needs-human
. Final: issue files left on disk, PRs ready for merge/automerge, tests/gates, skip reasons.
分类记录：
fixed-local
（本地已修复）、
ready-to-merge
（可合并）、
needs-fixup
（需修正）、
skipped
（已跳过）、
needs-human
（需人工处理）。 最终输出：磁盘上留存的问题文件、可合并/自动合并的PR、测试/关卡结果、跳过理由。