openclaw-pr-maintainer

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Maintaining a busy open-source repository like OpenClaw requires repetitive, error-prone work: triaging issues, finding duplicates, verifying contributor identity, reviewing PRs with provenance, and applying close labels consistently. This Skill encodes that maintainer workflow so reviews and triage decisions follow a consistent, evidence-based process. ## Core Features & Use Cases - Issue and PR triage with gitcrawl and gh: Search local gitcrawl data for duplicates and related threads, verify live state with the GitHub CLI, and select small, high-confidence fix candidates. - Opener identity and activity reports: Surface each issue/PR author's name, account age, OpenClaw-local activity, and global GitHub contributions via the bundled github-activity.sh script. - Structured PR review and landing hygiene: Enforce a best-fix verdict, provenance via git blame, LOC stats, evidence requirements, auto-close labels, and safe comment formatting. - Use Case: A maintainer pastes an OpenClaw PR URL and asks for a review; the Skill claims the PR, reports the author's activity, reads the surrounding code, and produces a findings-first review with provenance and a best-fix verdict. ## Quick Start Ask the assistant to review or triage a specific OpenClaw issue or PR by pasting its URL or number.

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 commands like threads, neighbors, and search against openclaw/openclaw to find related threads and duplicates, then verify live state with gh issue view or gh pr view before labeling or closing. Fall back to gh search when gitcrawl data is missing or stale.

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

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

What evidence is required before merging a bug-fix PR?

A bug-fix PR requires symptom evidence such as a repro or failing test, a verified root cause with file and line, blame-backed provenance when traceable, a fix touching the implicated path, and a regression test or documented manual verification.

When should issues be closed with auto-response labels instead of manual comments?

Apply r:* labels such as r: support, r: spam, or r: third-party-extension when an issue matches an auto-close reason, and let the auto-response workflow handle commenting and closing. Do not manually close and comment for those labeled reasons.

Does this workflow work without gitcrawl installed?

Yes, when gitcrawl is missing, stale, or lacks the target thread, the workflow falls back to GitHub search using gh search issues and gh search prs with title, body, and comment matching against the openclaw/openclaw repository.