openclaw-pr-maintainer

Automate GitHub pull request review and triage with evidence checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainer workflow for reviewing, triaging, preparing, closing, or landing OpenClaw pull requests and related issues. Use when Codex needs to validate bug-fix claims, search for related issues or PRs, apply or recommend close/reason labels, prepare GitHub comments safely, check review-thread follow-up, or perform maintainer-style PR decision making before merge or closure.

Core Features & Use Cases

  • Triage and labeling guidance: apply appropriate close and triage labels to PRs and issues to streamline review.
  • Evidence-driven landing: enforce documentation of symptoms, root cause, and verification before merging.
  • Safe communication templates: generate or guide comments that adhere to project guidelines and avoid exposing sensitive data.
  • Cross-referencing assistance: search for related issues/PRs to prevent duplicates and inform decisions.
  • Review hygiene automation: track activity and remind maintainers of follow-ups and deadlines.

Quick Start

Review the target PR, apply the recommended labels, prepare a safe landing comment, and verify required checks before 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 PR triage and maintainer decisions?

Automate GitHub PR triage by applying close and reason labels, checking required evidence, and preparing safe comments. This streamlines maintainer decision making during the pull request review and merge process.

What is evidence-driven landing in a pull request review workflow?

Evidence-driven landing enforces documentation of symptoms, root cause, and verification before merging. This ensures required checks are validated and prevents unsupported pull requests from landing.

How do I search for related issues and prevent duplicate pull requests?

Search for related issues and PRs using keyword-based queries to cross-reference existing work. This prevents duplicates and informs maintainer decisions during the review process.

Can I safely prepare GitHub comments during PR review without exposing sensitive data?

Generate safe communication templates that adhere to project guidelines and avoid exposing sensitive data. This enforces safe text handling in comments and follow-up actions.

Does this PR review workflow require any specific dependencies or components?

No specific dependencies or components are required. The workflow operates directly on GitHub pull requests and issues to apply labels, check evidence, and prepare comments.

How do I track review thread follow-ups and maintainer deadlines?

Track review thread activity to remind maintainers of follow-ups and deadlines. This review hygiene automation maintains workflow momentum across OpenClaw pull requests.