openclaw-pr-maintainer
Skill59 starsChanged 16 days agoMITView on GitHub
Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.
We split this skill into the rules it gives an agent
9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Review/triage/list: read-only; explain change/findings/proof/uncertainty.
- Distinctive: line 16
Queue/discovery: read triage. Batch live reads/shared discovery.
- Very specific: line 22
Start git status -sb; preserve unrelated work.
- Distinctive: line 35
Read owner, entry points, callers, siblings, tests, docs, history, current main.
- Distinctive: line 50
Before committing or landing nontrivial code: fresh review through permitted workflow.
- Distinctive: line 58
Verify remote merge/closure + source.
- Very specific: line 62
Never remove worktree holding live session cwd, including yours or subdirectories.
- Distinctive: line 64
Remove created worktrees once work/PR lands, unless immediately needed next.
- Very specific: line 65
Every task: findings in chat/stdout.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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. Localgitcrawl→ bare PATHgh, 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
CODEOWNERSroutes 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.mdrelease-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.
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 6
- steipete/warelay★ 394k73% same
- moltbot/clawdbot★ 394k73% same
- moltbot/moltbot★ 394k73% same
- clawdbot/clawdbot★ 394k73% same
- steipete/clawdis★ 394k73% same
- openclaw/openclaw★ 394k73% same
Wrote their own version · 9
- molt-bot/clawdbot★ 391ksame name
- OpenBMB/EdgeClaw★ 1.2ksame name
- friuns2/openclaw-android-assistant★ 573same name
- OpenClawAndroid/openclaw-android-assistant★ 556same name
- AtomicBot-ai/atomicbot★ 325same name
- QVerisAI/QVerisBot★ 184same name
- clawsouls/soulclaw★ 9same name
- hkyutong/OneClaw★ 1same name
- supermansuper563-ops/openclaw-workbench★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use openclaw-performance.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
clawdbotSkillopenclaw-performance
Performance work in OpenClaw: a slow or heavy flow (latency, CPU, memory, SQL, RPC, renders), writing or reviewing a perf PR, or adding a cache. Count the work, delete waste first, cache last.
Also in 6 projects that use this
In this repository107 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- extensions/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- test/AGENTS.mdAGENTS.md
- ui/AGENTS.mdAGENTS.md
- agent-transcriptSkill
- auto-qaSkill
- autoreviewSkill
- channel-message-flowsSkill
- clawdtributorSkill
- claw-scoreSkill
- clawsweeperSkill
- control-ui-e2eSkill
- crabboxSkill
- discord-clawdSkill
- discord-e2eSkill
- discord-user-postSkill
- discrawlSkill
- gitcrawlSkill
- graincrawlSkill
- notcrawlSkill
- openclaw-changelog-updateSkill
- openclaw-ci-limitsSkill
- openclaw-debuggingSkill
- openclaw-docker-e2e-authoringSkill
- openclaw-ghsa-maintainerSkill
- openclaw-live-updaterSkill
- openclaw-parallels-smokeSkill
- openclaw-qa-testingSkill
- openclaw-refactor-docsSkill
- openclaw-release-validationSkill
- openclaw-repair-sweepSkill
- openclaw-secret-scanning-maintainerSkill
- openclaw-test-heap-leaksSkill
- openclaw-testingSkill
- openclaw-test-performanceSkill
- openclaw-updateSkill
- parallels-discord-roundtripSkill
- plugin-sdk-impactSkill
- proof-videoSkill
- prototype-openclaw-tuiSkill
- pr-simplifySkill
- release-openclaw-announcementSkill
- release-openclaw-ciSkill
- release-openclaw-macSkill
- release-openclaw-maintainerSkill
- release-openclaw-plugin-testingSkill
- security-triageSkill
- slack-e2eSkill
- slacrawlSkill
- solidSkill
- tag-duplicate-prs-issuesSkill
- technical-documentationSkill
- telegram-e2e-userbotSkill
- test-auditSkill
- update-team-serverSkill
- verify-releaseSkill
- 1passwordSkill
- apple-notesSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

