openclaw-pr-maintainer

Review OpenClaw pull requests with labels, evidence checks, and landing guidance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainer workflows for reviewing, triaging, preparing, closing, or landing OpenClaw pull requests and related issues can be error-prone and time-consuming. This skill provides structured guidance to ensure consistent labeling, evidence-based decision making, and safe, efficient PR landings.

Core Features & Use Cases

  • Apply correct close and triage labels automatically when an issue or PR matches an auto close reason, and ensure downstream automation handles the response.
  • Enforce bug-fix evidence by requiring repros, logs, or failing tests before landing a patch.
  • Guide safe GitHub text handling and commenting to avoid formatting issues or malformed references.
  • Facilitate broad search across PRs and issues to surface related discussions before deciding on duplicates or closures.
  • Promote PR review hygiene and explicit follow-up actions, including scoped commits and avoiding bundling unrelated changes.
  • Ensure safety and process compliance with explicit checks before merge, including when an action would affect multiple PRs.

Quick Start

Review a new PR by checking auto close criteria, apply the correct labels, verify evidence requirements, and prepare the PR for landing.

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 pull request triage and labeling for bug fixes?

Automate GitHub pull request triage by applying correct close and triage labels automatically when a PR matches specific criteria, ensuring downstream automation handles the response without manual intervention.

What is the best way to enforce bug-fix evidence before landing a pull request?

Enforce bug-fix evidence by requiring repros, logs, or failing tests before landing a patch. This structured review process validates bug-fix claims and ensures safe, verified PR landings.

How do I search related issues to prevent duplicate pull request closures on GitHub?

Search related issues by facilitating broad searches across PRs and issues to surface related discussions before deciding on duplicates or closures, preventing erroneous issue management.

How do I ensure safe GitHub text handling when drafting PR comments?

Ensure safe GitHub text handling by following structured guidance for commenting that avoids formatting issues or malformed references when drafting PR review comments.

What PR review hygiene checks are needed before merging multiple pull requests?

PR review hygiene checks require explicit safety and process compliance verification before merge, including scoped commits and avoiding bundling unrelated changes when an action affects multiple PRs.