skills.rest
pertain99
pertain99COMMUNITY
Explore all skills by this author →
GitHub

openclaw-pr-maintainer

Automate OpenClaw pull request review, triage, and landing workflows.

1|Updated Apr 10, 2026
Search Tags:#github#process#triage#code-review#labels#pull-request#maintainer
One-click install
npx skills add https://github.com/pertain99/openclaw-better --skill openclaw-pr-maintainer-pertain99
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-pr-maintainer
Source: https://github.com/pertain99/openclaw-better/tree/main/.agents/skills/openclaw-pr-maintainer
Command: npx skills add https://github.com/pertain99/openclaw-better --skill openclaw-pr-maintainer-pertain99

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
  • Follow PR review and landing hygiene
  • Extra safety

Quick Start

Triage a newly opened PR by applying labels, verify bug-fix evidence, and prepare a safe landing plan.

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

Streamline PR triage by automatically applying labels, verifying bug-fix evidence, and preparing safe GitHub comments. This enforces prerequisite checks before merging or closing to maintain review hygiene.

What is the best way to verify bug-fix claims in a pull request?▼

Verify bug-fix claims by enforcing a strict evidence bar during code review. The workflow checks review-thread follow-ups and validates that claims meet required proof standards before proceeding to merge.

How do I apply close and triage labels correctly on GitHub pull requests?▼

Apply close and triage labels correctly using automated guardrails for auto-close reasons. This ensures prerequisite checks are met and safe comments are generated before executing merge or closure actions.

Can I automatically generate safe GitHub comments for PR review follow-ups?▼

Generate safe GitHub comments automatically for PR review follow-ups. The workflow handles GitHub text safely and manages review-thread follow-ups to prevent inappropriate or unsafe output during triage.

Does this PR review workflow work with OpenClaw projects on GitHub?▼

This workflow applies specifically to GitHub-based OpenClaw projects. It automates maintainer tasks during bug-fix verification, label management, and PR follow-ups for related issues.

Related Skills

Explore More Software Engineering Skills→
p-sree-sai-pavanp-sree-sai-pavan
5

clawdtributor

Triage OpenClaw PRs and issues with live GitHub status summaries.

Community
Advanced
kubiyabotkubiyabot
16

github-skill

Manage GitHub repositories, issues, pull requests, branches, releases, and actions via REST API.

Official
Advanced
JOHNNYWHITEMIKEJOHNNYWHITEMIKE

openclaw-pr-maintainer

Guide maintainer-grade triage and evidence-gated decisions for OpenClaw pull requests.

Community
Advanced
luyangliuableluyangliuable

fetch-unresolved-comments

Fetch unresolved pull request review comments from GitHub via GraphQL.

Community
Intermediate