openclaw-pr-maintainer

Triage GitHub issues and PRs using local gitcrawl data and live GitHub state.

5|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/p-sree-sai-pavan/P.A.R.K.E.R --skill openclaw-pr-maintainer-p-sree-sai-pavan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-pr-maintainer
Source: https://github.com/p-sree-sai-pavan/P.A.R.K.E.R/tree/main/gateway/.agents/skills/openclaw-pr-maintainer
Command: npx skills add https://github.com/p-sree-sai-pavan/P.A.R.K.E.R --skill openclaw-pr-maintainer-p-sree-sai-pavan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Maintainers need fast, reliable visibility into issues and PRs, including identity, account age, activity, and related threads, to make accurate triage and decision-making.

Core Features & Use Cases

  • Surface opener identity, activity history, and account age for issues and PRs.
  • Cluster related threads, surface duplicates, and provide labeling/close/land guidance.
  • Validate state with local gitcrawl data and live GitHub state to avoid expensive or unsafe actions.

Quick Start

Paste an OpenClaw issue/PR URL or number to begin maintainer-oriented triage and review.

Frequently Asked Questions about openclaw-pr-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage GitHub pull requests using maintainer insights?

Triage GitHub pull requests by pasting an issue or PR URL to surface opener identity, account age, and activity history. The tool clusters related threads, detects duplicates, and validates live GitHub state to guide labeling, closing, and landing decisions.

What is the best way to find duplicate issues in a GitHub repository?

Find duplicate issues by analyzing pasted URLs or numbers to cluster related threads using local gitcrawl data and live GitHub state. The tool surfaces duplicates and provides actionable recommendations for closing redundant issues.

Do I need gh and jq installed to review GitHub PR account history?

Yes, you need gh and jq installed in your current workspace to review GitHub PR account history. The tool relies on these dependencies along with gitcrawl and GitHub APIs to verify state and compute maintainer-oriented clusters.

Can I validate live GitHub state before deciding to close an issue?

Yes, you can validate live GitHub state before closing an issue to avoid unsafe actions. The tool cross-references local gitcrawl data with live GitHub API state to ensure accurate decision-making for labeling and closing threads.

How do I cluster related GitHub threads for pull request triage?

Cluster related GitHub threads by inputting PR numbers or URLs to compute relationships using local gitcrawl data and live GitHub state. The tool groups related issues and PRs to help maintainers identify duplicates and make landing decisions.

Does GitHub PR triage work without running expensive repository operations?

Yes, GitHub PR triage works without expensive operations by relying on local gitcrawl data and live GitHub API state. The tool intentionally avoids costly repository actions while computing clusters and presenting actionable recommendations.