openclaw-pr-maintainer

Automate OpenClaw PR review, triage, labeling, and merge preparation on GitHub.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/wuv-dreamguide/openclaw --skill openclaw-pr-maintainer-wuv-dreamguide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-pr-maintainer
Source: https://github.com/wuv-dreamguide/openclaw/tree/main/.agents/skills/openclaw-pr-maintainer
Command: npx skills add https://github.com/wuv-dreamguide/openclaw --skill openclaw-pr-maintainer-wuv-dreamguide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainer workflow for reviewing, triaging, preparing, closing, or landing OpenClaw pull requests and related issues. Use when ensuring correct labeling, safe commenting, evidence-based decisions, and consistent merge hygiene before release.

Core Features & Use Cases

  • Apply close and triage labels correctly to align with automation rules.
  • Enforce the bug-fix evidence bar by requiring concrete repros, root cause analysis, and tests before landing.
  • Handle GitHub text safely by guiding how to compose comments and PR updates without unsafe content.
  • Search broadly before deciding to avoid duplicates and mis-labeled issues, using comprehensive triage.
  • Follow PR review and landing hygiene, including committer workflow and standardized templates.
  • Extra safety: guardrails to prevent unsafe actions and ensure auditability.

Quick Start

Run the maintainer workflow to triage a new PR and prepare a safe landing plan.

Frequently Asked Questions about openclaw-pr-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub PR triage and labeling for incoming pull requests?

Automating GitHub PR triage applies predefined rules to label incoming pull requests and issues correctly. It enforces consistent labeling aligned with automation rules before merging on GitHub.

What is the best way to enforce evidence-based bug fix reviews before merging?

Enforcing the bug-fix evidence bar requires concrete reproductions, root cause analysis, and tests before landing. This ensures evidence-based decisions are met during the PR review process.

How do I safely compose GitHub comments and PR updates without unsafe content?

Safely composing GitHub comments involves following safe text handling guardrails to prevent unsafe content. It guides how to prepare comments and PR updates without triggering unsafe actions.

Can I use a committer workflow to standardize PR landing hygiene on GitHub?

Yes, following PR landing hygiene includes a committer workflow and standardized templates. It ensures consistent merge hygiene and auditability before release.

Why should I search broadly before deciding to close or won't fix GitHub issues?

Searching broadly before deciding avoids duplicates and mis-labeled issues during comprehensive triage. It supports drafting accurate close or won't fix decisions for GitHub issues.

Does automated PR review handle guardrails to prevent unsafe maintainer actions?

Yes, extra safety guardrails prevent unsafe actions and ensure auditability during maintainer review. They protect the workflow when triaging, labeling, and landing OpenClaw pull requests.