openclaw-pr-maintainer

Automates OpenClaw GitHub issue triage, PR review, and maintainer workflows using gitcrawl and gh.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill openclaw-pr-maintainer-jerome-prakash-l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-pr-maintainer
Source: https://github.com/JEROME-PRAKASH-L/openclaw/tree/main/.agents/skills/openclaw-pr-maintainer
Command: npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill openclaw-pr-maintainer-jerome-prakash-l

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Maintaining a high-volume open-source repository like OpenClaw requires repetitive, error-prone work: triaging issues, finding duplicates, verifying bug claims, reviewing PRs, and deciding what to close or land. This Skill standardizes that maintainer workflow with evidence-based procedures so reviews and triage decisions are consistent and auditable. ## Core Features & Use Cases - Issue and PR triage with gitcrawl: Search local thread data, find duplicates and clusters, and verify live state with gh before commenting, labeling, or closing. - Opener identity and activity reports: Surface author name, account age, and 12-month OpenClaw/GitHub activity via the bundled github-activity.sh script. - Structured PR review: Enforce a best-fix verdict, provenance via git blame, LOC stats, alternatives considered, and an evidence bar before landing bug fixes. - Use Case: A maintainer pastes an OpenClaw PR URL and asks for a review; the Skill checks assignment, reads the diff plus surrounding code, verifies the root cause with blame, and outputs findings with a best-fix verdict. ## Quick Start Review OpenClaw PR number 12345 and tell me whether it is the best fix for the linked issue.

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 OpenClaw GitHub issues with gitcrawl?

Start with gitcrawl to query local thread data, find neighbors and duplicates, and cluster related issues. Then verify live state with gh issue view or gh api before commenting, labeling, or closing anything.

How do I review an OpenClaw pull request before merging?

Check assignment first, then read the diff plus surrounding callers, callees, and tests. The review must include findings, LOC stats, blame-based provenance for regressions, a best-fix verdict, and alternatives considered.

How do I check a GitHub user's account age and activity?

Run the bundled github-activity.sh script with the user's login to get account creation date, OpenClaw-local PRs, issues, and commits over 12 months. Add the --global flag for public GitHub contribution totals.

What should I do if gitcrawl data is missing or stale?

Fall back to the GitHub search workflow using gh search issues and gh search prs with --match title,body. Avoid running expensive gitcrawl sync or reclustering commands unless the user explicitly asked to update the local store.

When should an OpenClaw issue or PR be closed?

Apply an auto-close label like r: support or r: spam and let the auto-response workflow handle closing. For items already fixed on main, comment with proof and the canonical commit or release, then close manually.

Does this workflow require evidence before merging bug fixes?

Yes. Landing a bug fix requires symptom evidence, a verified root cause with file and line, blame-backed provenance, a fix touching the implicated path, and a regression test or documented manual verification.