openclaw-pr-maintainer

Automate GitHub repository maintenance with issue triage and pull request review.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

This skill automates the high-friction, repetitive tasks associated with maintaining the OpenClaw repository, such as triaging issues, reviewing pull requests, and verifying contributor identity.

Core Features & Use Cases

  • Automated Triage: Uses gitcrawl and GitHub CLI to cluster issues, identify duplicates, and surface high-confidence candidates for maintainers.
  • Contributor Identity Verification: Automatically fetches and summarizes contributor activity, account age, and history to help maintainers assess trust and context.
  • Review Hygiene: Enforces consistent PR review standards by checking code paths, dependency contracts, and evidence-based bug verification before landing changes.

Quick Start

Use the openclaw-pr-maintainer skill to triage the latest open issues and summarize the activity of the author for PR number 123.

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 review and issue triage for my repository?

Automated GitHub pull request review and issue triage clusters threads, verifies bug fixes, and enforces landing hygiene using GitHub CLI and local gitcrawl data to deliver evidence-based maintainer decisions.

What is the best way to verify contributor identity and activity history before merging a pull request?

Verifying contributor identity and activity history involves fetching GitHub account age, contribution frequency, and past repository activity to generate a summarized trust assessment for maintainers.

How do I identify duplicate issues and cluster related threads in GitHub?

Identifying duplicate issues and clustering related GitHub threads requires analyzing issue metadata and content with gitcrawl data to surface high-confidence candidates for maintainer action.

Do I need GitHub CLI and jq installed to automate repository maintenance tasks?

Automating repository maintenance tasks requires GitHub CLI and jq as dependencies, alongside local gitcrawl data, to query repository threads and parse JSON responses for evidence-based review decisions.

Can I enforce consistent PR review standards by checking code paths and dependency contracts?

Enforcing consistent PR review standards checks code paths, dependency contracts, and evidence-based bug verification before landing changes to maintain strict repository hygiene across merged pull requests.