Engineering
openclaw-pr-maintainer avatar

openclaw-pr-maintainer

Automated OpenClaw repository maintainer: triage, label, and validate PRs/issues using gitcrawl and GitHub CLI.

Introduction

The openclaw-pr-maintainer skill acts as a specialized assistant for repository managers, streamlining the intake and maintenance of GitHub issues and pull requests in the OpenClaw ecosystem. It is designed to handle high-volume triage by leveraging local repository context via gitcrawl, ensuring that only high-confidence, evidence-backed changes proceed to landing. The skill is intended for maintainers and core contributors who need to enforce rigorous engineering standards, such as verifying regression tests, confirming root causes, and filtering out low-signal submissions like redundant refactors or unsupported third-party extensions.

  • Automated triage using gitcrawl for thread discovery, clustering, and duplicate detection.

  • Rigorous evidence verification: requires repro steps, log output, or failing tests before allowing PR merges.

  • Intelligent labeling system integrated with OpenClaw's auto-response workflows for categories like support, spam, or invalid requests.

  • Search and discovery features using hybrid query modes to identify relevant PRs across the repository history.

  • Operational safety: strictly read-only for initial analysis with explicit authorization for mutating operations like closing, labeling, or merging.

  • Always start sessions with gitcrawl commands to utilize cached local embeddings before hitting the live GitHub API.

  • When triaging, prioritize candidates that show a clear regression test or narrow scope to minimize the risk of regressions in core components.

  • Use the provided r:* labels to trigger existing CI/CD automation workflows rather than performing manual cleanup.

  • Avoid broad, expensive sync operations unless explicitly requested to update local store data.

  • Strictly enforce the evidence bar; if a PR lacks a verified root cause or regression test, request additional documentation or proof instead of approving.

  • Maintain safe interaction with GitHub text by using shell-safe heredocs, ensuring that complex code snippets or logs are not mangled by shell interpreters.

Repository Stats

Stars
366,610
Forks
75,248
Open Issues
6,919
Language
TypeScript
Default Branch
main
Sync Status
Idle
Last Synced
Apr 30, 2026, 10:40 AM
View on GitHub