$ ~/registry/skill/openclaw-agents-skills-openclaw-pr-maintainer

SKILL

openclaw-pr-maintainer

Name: openclaw-pr-maintainer
Author: openclaw

Review, triage, and manage OpenClaw issues and pull requests faster.

Stars

★ 382,582

Source

GitHub

Updated

2026-07-11

// securityCaution

Prompt only, no code
Open source
Community-trusted· 377.5k

Summary

The material indicates this is essentially a maintainer-facing prompt workflow for OpenClaw, and the system flags it as prompt-only with no required secrets or declared remote endpoints, so overall risk is low. Caution is still warranted because the README references gh/gitcrawl commands and GitHub maintenance actions; if the host environment actually grants such tools, they introduce normal data-access and repository-operation considerations.

CredentialsLow risk

The material explicitly states that no keys or environment variables are required, and it does not request tokens, API keys, or other sensitive credentials, so credential exposure risk appears low.

Network egressLow risk

The system marks it as prompt-only and no remote endpoints are declared. While the material mentions GitHub search and gh/api workflows, it does not show the skill itself configuring any separate data-exfiltration destination.

Code executionCaution

The README explicitly includes command examples for gitcrawl, gh, and gh api, and instructs maintainer actions such as commenting, labeling, closing, and landing. If the host permits tool use, this is normal local command/repository-operation capability that warrants caution for operational mistakes, but not a high-risk rating by itself.

Data accessCaution

The material points to reading local gitcrawl data, the current checkout, and GitHub repository metadata such as issues/PRs, comments, labels, assignees, and timelines. This access scope is broadly consistent with its stated maintainer workflow purpose, with no clear sign of excessive authorization in the text.

Supply chainLow risk

The source is a GitHub open-source repository with extremely high community adoption (about 377k stars), which materially lowers supply-chain risk. Although the license is unspecified and maintenance status is unknown, the available evidence still supports a low-risk assessment.

Recommendations

If used in an environment with gh/gitcrawl capabilities, verify issue/PR state in read-only mode before performing close, label, or merge actions.
Confirm the actual GitHub permission scope granted by the host, and avoid using an account with privileges beyond what maintenance requires.
Review the skill definition and related prompt files in the repository to confirm there are no additional undisclosed automated actions.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "openclaw-pr-maintainer" skill from askskill:
1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/openclaw-pr-maintainer/SKILL.md
2. Save it as ~/.claude/skills/openclaw-pr-maintainer/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Review PR risk

Prompt

Please review this OpenClaw PR: https://github.com/.../pull/123. Summarize the changes, identify risks, note any missing tests, and recommend whether it should be merged.

Expected

A concise review with change summary, risks, test coverage notes, and a merge recommendation.

Triage and duplicate search

Prompt

Please handle this OpenClaw issue: #456. Determine the issue type and priority, search for duplicates, and suggest appropriate labels.

Expected

A triage result including priority, duplicate links, suggested labels, and next-step recommendations.

Check contributor credibility

Prompt

Please analyze the contributor behind PR #789. Check the author's account age, activity, past contributions, comment history, and whether maintainer attention is needed.

Expected

A contributor background summary with a credibility assessment and any signs that warrant manual review.

// docs

OpenClaw PR Maintainer

Use this skill for maintainer-facing GitHub workflow, not for ordinary code changes.

Start issue and PR triage with gitcrawl

Use $gitcrawl first anytime you inspect OpenClaw issues or PRs.
Check local gitcrawl data first for related threads, duplicate attempts, and already-landed fixes.
Use gitcrawl for candidate discovery and clustering; use gh, gh api, and the current checkout to verify live state before commenting, labeling, closing, or landing.
If gitcrawl is missing, stale, lacks the target thread, or has no embeddings for neighbor/search commands, fall back to the GitHub search workflow below.
Do not run expensive/update commands such as gitcrawl sync --include-comments, future enrichment commands, or broad reclustering unless the user asked to update the local store or stale data is blocking the decision.

Common read-only path:

gitcrawl threads openclaw/openclaw --numbers <issue-or-pr-number> --include-closed --json
gitcrawl neighbors openclaw/openclaw --number <issue-or-pr-number> --limit 12 --json
gitcrawl search openclaw/openclaw --query "<scope or title keywords>" --mode hybrid --json
gitcrawl cluster-detail openclaw/openclaw --id <cluster-id> --member-limit 20 --body-chars 280 --json

Claim specific review targets

When a maintainer asks Codex to review, triage, fix, or land a specific OpenClaw issue/PR, check assignment before deep work.

Identify the requesting maintainer's GitHub login. In this environment, default Peter to steipete; if another maintainer is clearly the requester, use that maintainer's bare login.
Read current assignees with live gh issue view / gh pr view; gitcrawl is not enough for assignment state.
If unassigned, assign the requester before deep review. This is allowed for specific requested targets; do not auto-assign broad discovery candidates or shortlists.
If assigned to someone else, say so clearly before analysis and include assignment age:
- fresh: assigned within 6h; treat as actively owned unless user explicitly asks to continue or reassign
- stale: assigned 6h+ ago; treat as ownership hint, not a hard block; continue only with that caveat
If assigned to requester plus others, mention co-assignees and continue.
If assignment event time is unavailable, say assigned, time unknown; treat as assigned, not stale.
Never remove or replace assignees unless explicitly asked.

Assignment time proof:

gh api "repos/openclaw/openclaw/issues/<number>/timeline" --paginate \
  -H "Accept: application/vnd.github+json" \
  --jq '[.[] | select(.event=="assigned") | {assignee:.assignee.login, assigner:.assigner.login, actor:.actor.login, created_at}]'

Use the newest assigned event for each current assignee. Issue timeline events expose created_at; GitHub GraphQL AssignedEvent.createdAt is also valid when REST pagination is awkward.

Claim command for issues or PRs:

gh api -X POST "repos/openclaw/openclaw/issues/<number>/assignees" -f 'assignees[]=<login>' >/dev/null

Surface opener identity

For every reviewed, triaged, closed, or landed issue/PR, show the opener's human name when available, GitHub login, and account age.
Get the login from gh issue view / gh pr view (author.login), then fetch profile metadata once with gh api users/<login> --jq '{login,name,created_at,type}'.
Report opener identity as one compact line: By: Jane Doe (@jane, acct 2021-04-03) | OpenClaw: 4 PRs, 2 issues, 11 commits/12mo | GitHub: 9 repos, 86 commits, 9 PRs, 3 issues, 12 reviews
Always show recent activity in two lanes: OpenClaw-local PRs, issues, and commits in the last 12 months; and general public GitHub activity over the same window. For linked issue-fixing PRs, include both the PR author and issue opener when they differ.
Prefer the bundled helper for activity lookups:

…

View full docs ↗

Find and fix small high-confidence OpenClaw bugs ready to land.

openclawGet→

$ loading_