openclaw-pr-maintainer

Name: openclaw-pr-maintainer
Availability: InStock
Author: vut08905

Automate GitHub PR triage by applying labels and safe comments.

Updated Apr 7, 2026

Search Tags:#automation #github #triage #code-review #pull-request #maintainer

Ready to run

npx skills add https://github.com/vut08905/openclaw-app --skill openclaw-pr-maintainer-vut08905

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openclaw-pr-maintainer
Source: https://github.com/vut08905/openclaw-app/tree/main/.agents/skills/openclaw-pr-maintainer
Command: npx skills add https://github.com/vut08905/openclaw-app --skill openclaw-pr-maintainer-vut08905

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenClaw PR Maintainer provides a structured workflow to triage and close or land PRs and related issues, ensuring maintainers apply correct labels and follow up to preserve project quality.

Core Features & Use Cases

Apply close and triage labels correctly: When issues or PRs match auto-close reasons, the skill suggests labels and defers manual close.
Enforce bug-fix evidence bar: Before landing, require symptom evidence, root cause, and regression tests or explicit manual verification.
Handle GitHub text safely: Suggest safe comment formatting and avoid unsafe inline commands.
Search broadly before deciding: Before closing or merging, perform broad searches for related issues/PRs.

Quick Start

Review a pull request by validating evidence, applying appropriate labels, and preparing a safe final comment for merge.

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 apply labels safely?▼

Automating GitHub pull request triage involves applying labels and making decisions based on issue or PR content while requiring explicit evidence and guardrails to prevent unsafe actions or premature merges.

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

Enforcing a bug-fix evidence bar before landing a pull request requires validating symptom evidence, identifying the root cause, and ensuring regression tests or explicit manual verification exist.

Can I use automatic labeling rules for both GitHub issues and pull requests?▼

Automatic labeling rules can be applied across both GitHub issues and pull requests to suggest appropriate triage labels, though the workflow defers manual closure to the maintainer.

Does safe comment formatting matter during GitHub PR triage?▼

Safe comment formatting during GitHub PR triage ensures you avoid unsafe inline commands, generating comments that reference related issues or PRs without executing unauthorized actions.

Why should I perform broad searches before closing or merging a GitHub pull request?▼

Performing broad searches before closing or merging a GitHub pull request ensures you find related issues or PRs, gathering the explicit evidence needed to preserve overall project quality.