openclaw-pr-maintainer
Maintainer workflow for reviewing, triaging, preparing, closing, or landing OpenClaw pull requests and related issues. Use when Codex needs to validate bug-fix claims, search for related issues or PRs, apply or recommend close/reason labels, prepare GitHub comments safely, check review-thread follow-up, or perform maintainer-style PR decision making before merge or closure.
npx skills add SafeAI-Lab-X/ClawKeeper --skill openclaw-pr-maintainer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 spe
- Apply close and triage labels correctly
- Enforce the bug-fix evidence bar
- Handle GitHub text safely
- Search broadly before deciding
- Follow PR review and landing hygiene
- Extra safety
gh search prs --repo openclaw/openclaw --match title,body --limit 50 -- "auto-update" gh search issues --repo openclaw/openclaw --match title,body --limit 50 -- "auto-update" gh search issues --repo openclaw/openclaw --match title,body --limit 50 \
What does the openclaw-pr-maintainer skill do?
Maintainer workflow for reviewing, triaging, preparing, closing, or landing OpenClaw pull requests and related issues. Use when Codex needs to validate bug-fix claims, search for related issues or PRs, apply or recommend close/reason labels, prepare GitHub comments safely, check review-thread follow-up, or perform maintainer-style PR decision making before merge or closure.
How do I install it?
Run `npx skills add SafeAI-Lab-X/ClawKeeper --skill openclaw-pr-maintainer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From SafeAI-Lab-X/ClawKeeper, a repository with 1,034 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.