What problem does it solve? Maintaining a busy open-source repository requires consistent triage, evidence-based bug-fix review, and safe GitHub comment handling, which is error-prone when done ad hoc. This Skill encodes the maintainer decision workflow so PRs and issues are labeled, verified, and landed correctly. ## Core Features & Use Cases - Label-driven triage: Apply r:* close-reason labels (e.g., r: spam, r: support, invalid, dirty) and let the auto-response workflow handle comment, close, and lock actions. - Bug-fix evidence bar: Require symptom evidence, a verified root cause with file/line, a fix touching the implicated code path, and a regression test or documented manual verification before merging. - Safe GitHub commenting and search: Use single-quoted heredocs for multiline comments, avoid backtick-wrapping issue refs, and run broad gh search queries with --match title,body before closing as duplicate. - Use Case: A maintainer receives a bug-fix PR claiming to resolve an issue. Use this Skill to verify the repro evidence and root cause, search for duplicate issues, request changes if unsubstantiated, and land the PR following the /landpr process. ## Quick Start Review pull request 1234 in the openclaw/openclaw repository, verify its bug-fix evidence, and either request changes or prepare it for landing.
