Core Functions & Standard Workflow
1. Intelligent Retrieval & Triage
Local Cache Priority
All relevant threads, duplicate Issues and resolved patches are first queried from local archives via gitcrawl commands to boost throughput and reduce GitHub API traffic.
Candidate Filtering
When screening actionable Issues, pull requests submitted by core maintainers (e.g. @vincentkoc, @Takhoffman) within the last 14 days are automatically suppressed. External contributor PRs are prioritized for review.
Target Assignment Logic
Check assignment status before reviewing a specific Issue or PR:
- If unassigned, automatically assign the thread to the requesting reviewer
- If already assigned to another user, surface clear notification and evaluate ownership recency (ownership within 6 hours counts as active occupancy)
2. Contributor Identity & Activity Analysis
Automated Profile Lookup
For every Issue/PR under review, the skill automatically extracts and reports the submitter’s display name, GitHub handle, account age and historical contribution record.
Dual-Track Activity Summary
A compact single-line report displays two activity metrics as triage signals:
- Project-specific activity (PRs, Issues, commits submitted to OpenClaw over the past 12 months)
- Global cross-repository GitHub activity
3. Rigorous PR Review Protocol
Preliminary Change Context Summary
Before initiating formal review, write a 1–3 sentence plain-language breakdown explaining what the PR modifies and its core business impact.
Surrounding Code Audit
Review scope extends beyond modified diff lines; inspect caller functions, callee implementations, data contracts and adjacent test suites to map full runtime boundaries.
Optimal Fix Evaluation
Explicitly answer the judgment question: Is this the optimal resolution, or merely a functional workaround? At minimum one alternative implementation must be analyzed and rejected with documented reasoning before delivering a final verdict.
Defect Provenance Tracing
For bug-fix PRs, use git blame and similar utilities to trace the originating code change. Distinguish separate roles: original code author, PR submitter, and PR merger.
4. Strict Landing & Closing Eligibility Rules
Evidence-Based Merging
Bug-fix PRs must never be merged based solely on textual descriptions within Issues or PR bodies. Reproducible supporting artifacts (reproduction steps, error logs, failing test cases) are mandatory, and the patch must modify the exact faulty code path.
Crabbox E2E Validation Priority
End-to-end verification via the $crabbox environment is preferred over unit test validation alone whenever feasible.
Selective Low-Quality PR Closure
Explicit criteria define PRs eligible for direct closure: empty no-op changes, trivial arbitrary documentation edits, test coverage adjustments with no functional impact, third-party plugin maintenance work. Focused bug fixes and threads with active ongoing discussion are retained or escalated instead.
Safe Comment Text Handling
All Issue/PR comment generation must use literal multi-line strings or heredoc syntax to eliminate shell injection and parsing failures triggered by special characters such as backticks.
5. Standardized Review Output Format
All PR review reports must follow fixed structured sections:
- Findings: Identified defects, risks and improvement points
- LOC: Total lines of code modified
- Best-fix verdict: Final judgment on whether the patch is the optimal resolution
- Alternatives considered: Documented alternative implementations and rejection rationales
- Code read: Full list of source files audited during review
- Remaining uncertainty: Unresolved ambiguities or unvalidated edge cases
Release documentation references are strictly forbidden within review outputs; changelog maintenance belongs exclusively to post-release workflows and is out of scope for code review.
Primary Use Cases
- Daily Maintainer Triage
Rapidly surface high-priority, actionable external contributor PRs from large volumes of open threads, while automating contributor identity validation and thread assignment logic.
- In-Depth Rigorous Code Review
Enforce full contextual and runtime analysis beyond surface diff inspection, enabling consistent expert judgment on whether a submitted patch represents the optimal solution.
- Standardized Automated Landing & Closing
Implement uniform evidence-based thresholds for merging and closing pull requests to reduce subjective human bias and enforce baseline codebase quality standards.
- Clear Defect Accountability Tracing
Trace regressions back to the originating PR, original author and merger to support structured post-incident team retrospectives.
Summary
OpenClaw PR Maintainer is a highly automated, standardized GitHub workflow skill built exclusively for OpenClaw core maintainers. It codifies industry-standard open-source maintenance best practices — external contributor prioritization, evidence-only merging rules, full-context deep code review — into enforceable automated workflows. The tool improves operational efficiency and consistent quality control for large-scale open-source repository management.
