openclaw-pr-maintainer

Automate maintainer PR and issue triage with evidence-based labeling and comments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenClaw PR Maintainer helps maintainers triage, label, close, comment on, or land PRs/issues with evidence checks, reducing manual noise and speeding decision-making.

Core Features & Use Cases

  • Auto-labeling and triage based on maintainer evidence checks
  • Guided workflow for common maintainer decisions on PRs and issues
  • Use Case: A PR with insufficient evidence can be flagged and commented automatically, prompting the author to provide root cause or tests.

Quick Start

Run the maintainer workflow to automatically apply appropriate labels and triage PRs according to the maintainer policy.

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 PR triage and labeling on GitHub?

Automating PR triage uses policy-driven rules to evaluate pull requests, assign correct labels, and trigger auto-comments. This reduces manual maintainer noise by flagging insufficient evidence and prompting authors for root causes or tests.

What are evidence-based checks for GitHub pull requests?

Evidence-based checks validate that a PR includes required documentation like root causes or tests before proceeding. If evidence is missing, the workflow automatically flags the PR and comments to prompt the author for the necessary details.

Can I configure custom labeling rules for maintainer workflows?

You can configure custom labeling rules for maintainer workflows to guard against unsafe actions. The workflow implements policy-driven label assignment and safe review steps, allowing maintainers to define specific criteria for triage.

How do I automatically flag PRs with insufficient evidence?

Automatically flagging PRs with insufficient evidence triggers when policy checks detect missing root causes or tests. The workflow applies appropriate labels and generates auto-comments prompting the author to provide the required information.

Does this triage workflow support both GitHub issues and PRs?

This triage workflow supports both GitHub issues and PRs within the OpenClaw project. It applies maintainer evidence checks, labeling, commenting, and decision logging across both types of contributions to streamline repository management.