openclaw-pr-maintainer

Automate OpenClaw pull request triage, labeling, and evidence enforcement.

1.0k|59|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/SafeAI-Lab-X/ClawKeeper --skill openclaw-pr-maintainer-safeai-lab-x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-pr-maintainer
Source: https://github.com/SafeAI-Lab-X/ClawKeeper/tree/main/legacy/clawkeeper-watcher/.agents/skills/openclaw-pr-maintainer
Command: npx skills add https://github.com/SafeAI-Lab-X/ClawKeeper --skill openclaw-pr-maintainer-safeai-lab-x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainer workflows for reviewing, triaging, preparing, closing, or landing OpenClaw PRs and related issues, with guidance on labeling, evidence requirements, and safe messaging.

Core Features & Use Cases

  • Enforce correct labeling using predefined rules for auto-close reasons.
  • Ensure bug-fix evidence is provided before landing PRs (logs, repro, or tests).
  • Provide safe, maintainer-focused guidance for PR comments and follow-ups.

Quick Start

Command the PR Maintainer to triage a pull request by applying appropriate labels and composing safe maintainer comments.

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 my repository?

Automating GitHub pull request triage applies predefined rules to assign labels and enforce evidence requirements before merging. This workflow ensures bug fixes include logs or tests, and generates safe maintainer comments for follow-up management.

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

Enforcing bug-fix evidence requires logs, repro steps, or tests before a pull request can be merged. This structured guardrail ensures code references and validation are provided, preventing premature merges and maintaining repository stability.

Can I use automated workflows to generate safe comments for PR follow-ups?

Automated workflows can generate safe comments for PR follow-ups by applying maintainer-focused guidance. This ensures structured messaging and guardrails are satisfied before changes are merged, keeping communication consistent across GitHub repositories.

Does GitHub PR triage require predefined rules for auto-close reasons?

GitHub PR triage requires predefined rules for auto-close reasons to ensure correct labeling. Applying these structured guardrails maintains consistency when closing or landing pull requests and related issues across repositories.

How do I manage pull request follow-up tasks across multiple GitHub repositories?

Managing PR follow-up tasks across GitHub repositories uses automation to track labeling, evidence enforcement, and safe comment generation. This ensures structured guardrails are satisfied before changes are merged, keeping maintainer workflows consistent.

Why should I use structured guardrails for reviewing and landing pull requests?

Structured guardrails for reviewing pull requests require evidence, code references, and safe messaging before changes are merged. This prevents incomplete bug fixes, ensures correct labeling, and maintains repository quality during triage.