openclaw-pr-maintainer

Name: openclaw-pr-maintainer
Availability: InStock
Author: bitan-del

Triage and validate OpenClaw PRs and issues for safe merging.

4|2|Updated Mar 26, 2026

Search Tags:#automation #github #evidence #labeling #bugfix #pr-review #maintainer

Ready to run

npx skills add https://github.com/bitan-del/gods-eye --skill openclaw-pr-maintainer-bitan-del

💬 Prompt for ChatGPT / Claude Chat▼

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

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

Apply close and triage labels correctly
Enforce the bug-fix evidence bar
Handle GitHub text safely and search broadly before deciding
Follow PR review and landing hygiene
Extra safety measures to guard against unsafe actions and miscommunication

Quick Start

Run the maintainer workflow on a new PR to triage, label, and prepare a safe merge decision.

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 and labeling by validating bug-fix claims, applying correct close/reason labels, and enforcing review hygiene before a safe merge. It orchestrates maintainer-style decision making across pull requests and issues.

What is the best way to validate bug-fix evidence in a pull request before merging?▼

Validate bug-fix evidence in a pull request by enforcing a strict evidence bar, searching broadly for related issues, and verifying claims before applying triage labels or preparing a safe merge decision.

How do I ensure safe text handling when preparing GitHub comments for PR review?▼

Ensure safe text handling when preparing GitHub comments by applying extra safety measures that guard against unsafe actions and miscommunication during PR review and follow-up communication.

Can I use this to check review-thread follow-up and apply triage labels across GitHub issues and PRs?▼

Yes, you can check review-thread follow-up and apply triage labels across GitHub issues and PRs. It handles maintainer workflows covering evidence verification, labeling rules, and follow-up communication.

What are the limitations of automated PR review and merge decision workflows?▼

Automated PR review and merge decision workflows require explicit guidance on labeling rules and evidence collection to avoid unsafe actions. Decisions must remain auditable, and safe text handling is enforced to prevent miscommunication.