From fc334cda13224acff811e062db19f704f8279b56 Mon Sep 17 00:00:00 2001 From: Vincent Koc Date: Sat, 25 Apr 2026 16:48:35 -0700 Subject: [PATCH] chore(pr-triage): route low-signal cleanup to ClawHub --- .agents/skills/openclaw-pr-maintainer/SKILL.md | 15 +++++++++++++++ .github/workflows/auto-response.yml | 4 ++-- 2 files changed, 17 insertions(+), 2 deletions(-) diff --git a/.agents/skills/openclaw-pr-maintainer/SKILL.md b/.agents/skills/openclaw-pr-maintainer/SKILL.md index 20eab932433..ff03e429131 100644 --- a/.agents/skills/openclaw-pr-maintainer/SKILL.md +++ b/.agents/skills/openclaw-pr-maintainer/SKILL.md @@ -35,6 +35,21 @@ Use this skill for maintainer-facing GitHub workflow, not for ordinary code chan - If the claim is unsubstantiated or likely wrong, request evidence or changes instead of merging. - If the linked issue appears outdated or incorrect, correct triage first. Do not merge a speculative fix. +## Close low-signal manual PRs carefully + +- Do not close for red CI alone. Require a clear low-signal category plus stale or failed validation. +- Good manual-close categories: + - blank or mostly untouched PR template with no concrete OpenClaw problem/fix + - random docs-only churn such as root README translations, generic wording tweaks, or community-plugin discoverability docs that should go through ClawHub + - test-only coverage without a linked bug, owner request, or behavior change + - refactor-only cleanup, variable renames, formatting, or generated/baseline churn without maintainer request + - third-party channel/provider/tool/skill/plugin work that belongs on ClawHub instead of core + - 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 + - dirty branches where a narrow stated change includes unrelated docs/generated/runtime/extension files + - repeated bot-review spam or copied bot output without author-owned fixes +- Keep or escalate plausible focused bug fixes, green PRs, active maintainer discussions, assigned work, recent author follow-up, and unique reproduction details. +- For third-party capabilities, prefer the `r: third-party-extension` auto-response label when it applies; it points contributors to publish on ClawHub. + ## Handle GitHub text safely - For issue comments and PR comments, use literal multiline strings or `-F - <<'EOF'` for real newlines. Never embed `\n`. diff --git a/.github/workflows/auto-response.yml b/.github/workflows/auto-response.yml index 159337b8e33..f49fcdc4ff4 100644 --- a/.github/workflows/auto-response.yml +++ b/.github/workflows/auto-response.yml @@ -48,7 +48,7 @@ jobs: label: "r: skill", close: true, message: - "Thanks for the contribution! New skills should be published to [Clawhub](https://clawhub.ai) for everyone to use. We’re keeping the core lean on skills, so I’m closing this out.", + "Thanks for the contribution! New skills should be published on [ClawHub](https://clawhub.ai) for everyone to use. We’re keeping the core lean on skills, so I’m closing this out.", }, { label: "r: support", @@ -81,7 +81,7 @@ jobs: label: "r: third-party-extension", close: true, message: - "Please make this as a third-party plugin that you maintain yourself in your own repo. Docs: https://docs.openclaw.ai/plugin. Feel free to open a PR after to add it to our community plugins page: https://docs.openclaw.ai/plugins/community", + "Please publish this as a third-party plugin on [ClawHub](https://clawhub.ai) instead of adding it to the core repo. Docs: https://docs.openclaw.ai/plugin and https://docs.openclaw.ai/tools/clawhub", }, { label: "r: moltbook",