docs: clarify autoreview follow-up scope · openclaw/openclaw@c3baec7
steipete
·
2026-06-02
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -22,6 +22,8 @@ Use when:
|
22 | 22 | - Read dependency docs/source/types when the finding depends on external behavior. |
23 | 23 | - Reject unrealistic edge cases, speculative risks, broad rewrites, and fixes that over-complicate the codebase. |
24 | 24 | - Prefer small fixes at the right ownership boundary; no refactor unless it clearly improves the bug class. |
| 25 | +- When an accepted finding shows a bug class or repeated pattern, inspect the current PR scope for sibling instances before fixing. |
| 26 | +- Fix the scoped bug class at once when practical; stop at touched surfaces, owner boundaries, and clear follow-up territory. |
25 | 27 | - Keep going until structured review returns no accepted/actionable findings. |
26 | 28 | - If a review-triggered fix changes code, rerun focused tests and rerun the structured review helper. |
27 | 29 | - For security-audit suppression changes, verify accepted findings remain auditable: suppressed findings stay in structured output, active output keeps an unsuppressible suppression notice, and aggregate findings cannot hide unrelated active risk. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
