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.
Best for Project maintainersWorks with GitHub
⌘source
- author
@openclaw- language
- TypeScript
★360kstars
73kforks
Apr 17, 2026
✦overview.md
Key Features
- ·Applies auto-close labels for GitHub workflow automation
- ·Enforces strict bug-fix evidence requirements before merging
- ·Handles maintainer PR decision-making workflows
- ·Uses specific label taxonomy for triage
Use Cases
- →Reviewing pull requests that claim to fix bugs
- →Triage incoming issues for auto-close reasons
- →Preparing GitHub comments for maintainer responses
- →Validating bug-fix claims before merging code
Best for
- ✓Project maintainers
- ✓Code review automation
- ✓GitHub workflow management
Not ideal for
- !Ordinary code changes
- !Non-maintainer contributors
FAQs
name
openclaw-pr-maintainer
description
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.
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.ymlhandle 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: skillr: supportr: no-ci-prr: too-many-prsr: testflightr: third-party-extensionr: moltbookr: spaminvaliddirtyfor 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:
- symptom evidence such as a repro, logs, or a failing test
- a verified root cause in code with file/line
- a fix that touches the implicated code path
- 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.
$install
1-click copynpx skills add openclaw/openclaw --skill openclaw-pr-maintainerSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.