@@ -35,6 +35,21 @@ Use this skill for maintainer-facing GitHub workflow, not for ordinary code chan
3535- If the claim is unsubstantiated or likely wrong, request evidence or changes instead of merging.
3636- If the linked issue appears outdated or incorrect, correct triage first. Do not merge a speculative fix.
373738+## Close low-signal manual PRs carefully
39+40+- Do not close for red CI alone. Require a clear low-signal category plus stale or failed validation.
41+- Good manual-close categories:
42+- blank or mostly untouched PR template with no concrete OpenClaw problem/fix
43+- random docs-only churn such as root README translations, generic wording tweaks, or community-plugin discoverability docs that should go through ClawHub
44+- test-only coverage without a linked bug, owner request, or behavior change
45+- refactor-only cleanup, variable renames, formatting, or generated/baseline churn without maintainer request
46+- third-party channel/provider/tool/skill/plugin work that belongs on ClawHub instead of core
47+- risky ops/infra drive-bys such as new external CI services, release workflows, host upgrade scripts, Docker base migrations, or apt retry/fix-missing tweaks without owner request and green validation
48+- dirty branches where a narrow stated change includes unrelated docs/generated/runtime/extension files
49+- repeated bot-review spam or copied bot output without author-owned fixes
50+- Keep or escalate plausible focused bug fixes, green PRs, active maintainer discussions, assigned work, recent author follow-up, and unique reproduction details.
51+- For third-party capabilities, prefer the `r: third-party-extension` auto-response label when it applies; it points contributors to publish on ClawHub.
52+3853## Handle GitHub text safely
39544055- For issue comments and PR comments, use literal multiline strings or `-F - <<'EOF'` for real newlines. Never embed `\n`.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。