Skip to content
cccskills
FreePublished on GitHubEnglish overview

openclaw-pr-maintainer

Investigate OpenClaw issues and review pull requests, proposed code changes, using current source and test evidence. Depending on the authorized scope, repair defects locally or carry the change through review, merge, and final verification.

OriginalShow the original description

Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.

Works withGitHub
AI rating90/ 100See how to install

Good for

  • Reviewing an OpenClaw pull request
  • Investigating and repairing a reported defect locally
  • Checking whether an issue is already fixed
  • Completing an authorized merge and resolving CI failures

Overview

What it does

Investigate OpenClaw issues and pull requests, review them against current source code, and work through fixes and merging. It examines the proposed changes, callers, tests, and history to reproduce defects and verify repairs. If an issue appears resolved, it checks the relevant change and current behavior. When asked to merge, it addresses CI failures and conflicts and verifies completion on GitHub.

When it helps

Use it to assess whether a proposed change is appropriate or to fix a reported defect. It preserves contributors’ credit and unrelated work while explaining review findings and the limits of verification.

Example requests

  • “Review this OpenClaw PR and summarize findings supported by evidence.”
  • “Reproduce this issue, fix it locally, and verify the repair.”
  • “Merge this PR and confirm completion on GitHub.”

Notes

It uses Git, the GitHub CLI gh, and a working environment for the target repository. Review-only requests do not authorize edits or posting; local-fix requests do not authorize publication. Work follows the root AGENTS.md, CODEOWNERS, and required GitHub reviews. Significant code changes include an autoreview check.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Objective evaluation

AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.

Clear instructionsIs it clear when to use it and what it does?
AGoodIt defines separate scopes for review, local repair, and publication or merging.
Concrete stepsAre steps, inputs, outputs, and examples spelled out?
AGoodIt provides gh inspection commands and steps for reproduction, repair, validation, and remote completion checks.
SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt explicitly defines publication authority, required reviews, and protection of unrelated changes and credentials.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingIt uses gh and autoreview but does not provide installation or authentication procedures.

The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 19, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (7)

  • SKILL.md6.4 KB
  • references/attribution.md1.7 KB
  • references/landing-recovery.md15.4 KB
  • references/landing.md12.2 KB
  • references/media.md2.8 KB
  • references/triage.md2.3 KB
  • scripts/github-activity.sh6.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

OpenClaw PR Maintainer

  • Requested issue/PR operation only. Root AGENTS.md: repair, product, source-trust, approval policy. This skill: GitHub workflow.
  • Pasted ref ≠ publication permission or scope expansion.

Select the scope

  • Review/triage/list: read-only; explain change/findings/proof/uncertainty. Edits, assignment, labels, comments, closes need authority.
  • Fix only: investigate/repair/validate locally; publication needs ship/land or scoped equivalent.
  • Land/ship/autonomous repair: source proof → review → native submission → verified merge. Track pending requests; repair CI/conflicts under same authority. Accepted auto-merge ≠ done. Preserve credit/unrelated work; root gates remain, no repeat routine permission.
  • Queue/discovery: read triage. Batch live reads/shared discovery; named PR ≠ queue sweep.
  • Author/regression attribution: author and provenance research; account age/history conditional.
  • Lead hands-on; bounded useful workers, serialized checkout/refs + GitHub writes. No user-owned app tasks hiding internal subtasks. Preserve stalled worker patches/claims/proof before takeover/reassignment.

Inspect the actual item

  • Start git status -sb; preserve unrelated work. Local gitcrawl → bare PATH gh, narrow live JSON. Stale/missing archive → gh, no broad sync. PR source: gh pr view/diff + checkout, not web search.
gh pr view <pr> --repo openclaw/openclaw \
  --json number,title,state,body,author,assignees,baseRefName,headRefName,headRefOid,files,comments,reviews
gh issue view <issue> --repo openclaw/openclaw \
  --json number,title,state,body,author,assignees,comments
  • Assignment: triage, before deep work. Mention other assignees; preserve ownership. Account/activity research conditional.

Establish the outcome

  • Read owner, entry points, callers, siblings, tests, docs, history, current main; inspect determining dependency contracts. Codex: root's personal source inspection. Contrary evidence → investigate before defending. No invented matrix/alternative.
  • Already fixed: prove current-main repair; canonical commit/PR + matching source/runnable proof. Closure authority → comment evidence + close; otherwise report.
  • Real defect: reproduce → repair owning invariant → prove path/siblings. Simplification over symptom guard; size/LOC ≠ correctness gate.
  • Useful PR: improve editable branch; unsafe → authorized credited replacement before closure. Replaced ancestry → maintainer-owned replacement, never squash contributor PR.
  • Uncertain/product decision: state gap; no speculative merge/automatic out-of-scope close.
  • Proof + source-trust/host route: $openclaw-testing, landing. Focused proof → ready PR; PR CI = broad proof. Prefer bounded local proof on a qualified, available host. Deliberate remote proof can cover expensive checks or environment gaps; queues → stop task-owned allocation, use PR CI or a safe local scope, preserve uncovered requirements. Never execute untrusted source locally. Optional live gaps → meaningful boundary proof + limitation; explicit live, external API, authenticated-risk proof mandatory. Mocks/skips/old head ≠ live.
  • Behavioral changes: boundary-proof contract + $test-audit. Requested behavior and repo standards: check separately.

CODEOWNERS review

  • CODEOWNERS routes review; inspect live enforcement. Restricted/security paths + material product/behavior/security/ownership changes need listed-owner involvement.
  • ownership/review governance: verified active organization-admin direction also qualifies; repository admin/bypass alone does not. Neither route waives enforced reviews.

Review and publish

  • Before committing or landing nontrivial code: fresh review through permitted workflow; resolve actionable findings unless user opts out. Actionable = likely or high-impact; decline unlikely, recoverable edge cases whose fix adds disproportionate complexity, with one-line reason.

  • Nontrivial code commit/landing: $autoreview; resolve verified actionable findings. Review-only: independent pass only when requested, no extra mandatory CLI pass.

  • Reopen review for substantive changes/unresolved concerns, not patch-identical rebase/mechanical head change. Address real human/bot findings; explain rejections. Bot scores/Rank-up lists create no separate obligations. ClawSweeper advisory; never wait for comment to land.

  • Current PR template: plain problem/impact; inventories in diff/details. Keep risks, migrations, actions, proof, gaps, credit current; explain material tradeoffs. No invented internal-only user benefit or universal LOC/provenance/alternate-fix essays.

  • CHANGELOG.md release-owned; release-note context in PR/commit. Agent transcripts only on explicit request.

  • Public mutation: verify author/committer + writer; shell-sensitive body files. Authorized scope only; update existing comment/body, no duplicates.

  • Publication/merge: read landing (media, exact-head CI, native workflow).

  • Verify remote merge/closure + source. Report problem, owning change, proof/gaps, credit, linked final state in prose; worthwhile follow-ups only.

Finalize and clean up

  • Never remove worktree holding live session cwd, including yours or subdirectories. Child cd/cwd override does not move parent. Retain until owner exits/releases cwd; report path.
  • Verified outcome → remove task logs, receipts, proof archives, .crabbox, scratch, finished worktrees via native closeout. No retention/archive/export/handoff just for removal.
  • Remove created worktrees once work/PR lands, unless immediately needed next; never remove a live-cwd worktree.
  • Every task: findings in chat/stdout; files only for deliverables/tool/proof/recovery needs, state purpose/reuse. Pre-merge proof mandatory; optional follow-ups never hold completion.
  • Preserve requested deliverables/retention, unfinished source + necessary recovery state, active/live/unknown owners, credentials, agent state, shared dependencies.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

1password

FreeSummaryAI rating 100

Set up and authenticate the 1Password CLI, then supply stored passwords and API keys to commands or configuration. The skill covers desktop integration, service accounts, and interactive sign-in while keeping secrets out of chat and logs.

  • Setting up the 1Password CLI
  • Supplying API keys to commands
  • Using service account authentication in CI
openclaw/openclaw392.4KUpdated Oct 18, 2026

acp-router

FreeSummaryAI rating 80

Route requests from OpenClaw to external coding agents such as Claude Code or Cursor. Start or continue sessions using ACP, a protocol for connecting agents, or relay prompts directly through acpx while preserving conversation context.

  • Starting a Claude Code session in a thread
  • Continuing work with an external coding agent
  • Relaying prompts directly through acpx
openclaw/openclaw392.4KUpdated Oct 18, 2026

add-model-provider

FreeSummaryAI rating 100

Add a model provider to OpenClaw and verify it with a real response. The skill validates configuration, keeps credentials in environment or file references, and reports test results and any default model changes.

  • Adding a model provider to OpenClaw
  • Configuring credentials through environment or file references
  • Checking whether a model returns a real response
openclaw/openclaw392.4KUpdated Oct 18, 2026

agent-transcript

FreeSummaryAI rating 90

Prepare an agent activity transcript for a GitHub pull request or issue. Extract relevant prompts, decisions, and results from local logs, remove sensitive material, and preview the edited record before separately authorized publication.

  • Preparing an agent activity record for a pull request
  • Extracting task-relevant prompts and results from local logs
  • Previewing a transcript with sensitive information removed
openclaw/openclaw392.4KUpdated Oct 18, 2026

apple-notes

FreeSummaryAI rating 100

Manage Apple Notes on macOS through memo, a command-line tool. Create, browse, search, edit, delete, and move notes between folders, or export selected notes to HTML or Markdown for use outside the app.

  • Creating notes with titles
  • Finding notes by folder or approximate search
  • Editing notes and organizing them into folders
openclaw/openclaw392.4KUpdated Oct 18, 2026

apple-reminders

FreeSummaryAI rating 70

Manage Apple Reminders from your Mac with remindctl, a terminal tool. View tasks by date, add or edit reminders, organize lists, and mark tasks complete or delete them, including personal to-dos that sync to iOS.

  • Review today’s tasks and overdue reminders
  • Add personal to-dos with due dates
  • Organize tasks visible on an iPhone or iPad
openclaw/openclaw392.4KUpdated Oct 18, 2026

See all skills by openclaw

Report a problem with this skill