OpenClaw PR Maintainer

Use this skill for maintainer-facing GitHub workflow, not for ordinary code changes.

Apply close and triage labels correctly

• If an issue or PR matches an auto-close reason, apply the label and let .github/workflows/auto-response.yml handle the comment/close/lock flow.
• Do not manually close plus manually comment for these reasons.
• r:* labels can be used on both issues and PRs.
• Current reasons:
  • r: skill
  • r: support
  • r: no-ci-pr
  • r: too-many-prs
  • r: testflight
  • r: third-party-extension
  • r: moltbook
  • r: spam
  • invalid
  • dirty for PRs only

Enforce the bug-fix evidence bar

• Never merge a bug-fix PR based only on issue text, PR text, or AI rationale.
• Before landing, require:
  1. symptom evidence such as a repro, logs, or a failing test
  2. a verified root cause in code with file/line
  3. a fix that touches the implicated code path
  4. a regression test when feasible, or explicit manual verification plus a reason no test was added
• 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.

Handle GitHub text safely

• For issue comments and PR comments, use literal multiline strings or -F - <<'EOF' for real newlines. Never embed \n.
• Do not use gh issue/pr comment -b "..." when the body contains backticks or shell characters. Prefer a single-quoted heredoc.
• Do not wrap issue or PR refs like #24643 in backticks when you want auto-linking.
• PR landing comments should include clickable full commit links for landed and source SHAs when present.

Search broadly before deciding