openclaw-pr-maintainer

Enforce maintainer evidence checks when triaging OpenClaw PRs and issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers often struggle with consistent triage, labeling, and safe landings of PRs and issues in OpenClaw. This skill enforces evidence-driven reviews to streamline maintainer workflows.

Core Features & Use Cases

  • Apply close and triage labels correctly based on auto-close reasons and let automation handle comments, closes, and locks.
  • Enforce the bug-fix evidence bar by requiring concrete repros, root cause in code with file/line references, a tested fix, and regression verification where feasible.
  • Provide safe handling guidance for GitHub text and maintainers to reduce human error during comments and landings.
  • Support targeted maintainer workflows across multiple repositories with standardized triage and landings.

Quick Start

Review a PR or issue, verify maintainer evidence, and apply the correct labels before landing or closing.

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 maintainer workflows?

Automate GitHub PR triage by enforcing maintainer evidence checks to ensure consistent labeling and safe landings. This skill applies close and triage labels based on auto-close reasons, letting existing automations handle comments, closes, and locks across multiple repositories.

What evidence is required for a bug fix PR to pass code review triage?

Bug fix PR triage requires concrete repros, root cause in code with file and line references, a tested fix, and regression verification where feasible. This evidence bar ensures safe landings and standardized reviews across OpenClaw projects.

Can I use this triage skill across multiple GitHub repositories?

Yes, this skill supports targeted maintainer workflows across multiple GitHub repositories with standardized triage and landings. It integrates with existing automations and labeling schemes to maintain consistency across different OpenClaw projects.

How do I apply close and triage labels correctly when auto-closing GitHub PRs?

Apply close and triage labels correctly by matching auto-close reasons to the labeling scheme, then let automation handle the comments, closes, and locks. This reduces human error during maintainer text handling and PR landings.

What is the best way to ensure safe PR landings for OpenClaw projects?

Ensure safe PR landings by enforcing evidence-driven reviews that verify repros, root causes, and regression tests before applying labels. This skill provides safe handling guidance for GitHub text and maintainer workflows to reduce human error.

Why does my PR labeling scheme break when integrating with existing GitHub automations?

PR labeling schemes break when auto-close reasons are mismatched with triage labels or evidence checks are skipped. This skill standardizes labeling and integrates with existing automations to prevent inconsistent triage and unsafe landings.