What is openclaw-pr-batch-sweep?

A workflow for reviewing and landing batches of up to 20 low-risk contributor pull requests in the OpenClaw project. It covers choosing candidates, repairing changes, testing them, and merging them.

Use it for requests such as “next 20” or contributor pull-request sweeps, including duplicate discovery, maintainer review, testing, readiness checks, and landing suitable fixes.

It turns a large pull-request queue into bounded batches with documented decisions and checks. It also preserves earlier decisions so later runs do not repeat rejected or skipped work.

openclaw-pr-batch-sweep — Skill for Codex by vincentkoc

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add vincentkoc/dotskills --skill openclaw-pr-batch-sweep

Clone the repo

git clone --depth 1 https://github.com/vincentkoc/dotskills

Made for: Codex.

Its marketplace also offers this one on its own, as the plugin openclaw-pr-batch-sweep — /plugin install openclaw-pr-batch-sweep after adding the marketplace above.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/vincentkoc/dotskills/openclaw-pr-batch-sweep/github.svg)](https://agentmods.dev/skills/vincentkoc/dotskills/openclaw-pr-batch-sweep)

Your own site

<a href="https://agentmods.dev/skills/vincentkoc/dotskills/openclaw-pr-batch-sweep"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/openclaw-pr-batch-sweep/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/vincentkoc/dotskills/openclaw-pr-batch-sweep"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/openclaw-pr-batch-sweep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,121 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00095	$0.03121
Opus 5	$0.00048	$0.01561
Sonnet 5	$0.00019	$0.00624
Haiku 4.5	$0.00010	$0.00312

Measured 9d ago against content hash 6415aea4120f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

openclaw-pr-batch-sweep scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/hydrate-candidates.mjs, scripts/hydrate-candidates.test.mjs, scripts/rank-candidates.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/openclaw-pr-batch-sweep/SKILL.md · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpenClaw PR Batch Sweep

Purpose

Drive a continuing queue of real, low-risk OpenClaw contributor bug fixes through qualification, repair, proof, and landing. Work in batches of up to 20 without padding the batch with micro-patches, speculative cleanup, or risky surfaces.

Requires ghx, gitcrawl, gwt, and the OpenClaw maintainer, testing, autoreview, Crabbox, and ClawSweeper skills.

Read references/operator-selection-policy.md before selecting candidates. Read references/worker-contract.md before spawning sub-agents. Read and update references/decision-ledger.json so fresh runs inherit prior landed, rejected, closed, and explicitly skipped PRs.

Compose the repository skills instead of duplicating them:

$openclaw-pr-maintainer for live GitHub evidence and mutations.
$openclaw-landable-bug-sweep for proof, repair, and landing.
$gitcrawl for discovery and duplicate clusters.
$openclaw-testing, $crabbox, and $autoreview for validation.
$clawsweeper for readiness labels and exact-head review evidence.

When to use

The operator says next 20, continue the PR sweep, or asks for another batch.
The operator wants contributor PRs reproduced, narrowed, repaired, tested, and landed.
The queue must exclude drafts, maintainer-owned work, UI, security, SSRF, auth, config migrations, and high-risk changes.
Prior accept/reject decisions should shape future candidate selection.
Reuse a small retained worker pool so review scales without accumulating completed workers or creating noisy local process pressure.

Workflow

Recover and continue the existing queue.
- Read recent thread state and the batch ledger.
- Read auditWatermark when present. Use openPrThrough as the default floor for newly created PR discovery instead of rehydrating an unchanged live edge.
- The watermark is not a terminal decision. An older unhandled PR may re-enter only when its head SHA or risk/readiness state materially changed; terminal ledger entries never re-enter.
- Verify current main, live PR state, repo instructions, VISION.md, disk, and worktree health.
- Keep a handled set containing merged, closed, rejected, ignored, draft, and explicitly skipped PRs.
- Never recycle prior candidates merely because their metadata changed.

Read the full file on GitHub · 142 lines

Files

What ships with it

9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 142 lines · 95 tokens per session scan A 6415aea4120f

Subscribe to this mod's changes

openclaw-pr-batch-sweep is a skill published in the GitHub repository vincentkoc/dotskills (102 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 3,121 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Git and workflow LLM agentic-workflows ai-assistant automation codex developer-tools

github-commenting

How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.

juspay/neurolink · 41 tokens

github

GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…

yunze7373/openclaw-termux · 101 tokens

taiyi-integration

A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.

Dong90/oh-my-taiyiforge · 27 tokens

taiyi-review

A pre-merge review guide for checking code changes, design decisions, tests, and documentation. A merge adds reviewed changes to the main code branch.

Dong90/oh-my-taiyiforge · 26 tokens

verify-implementation

A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.

sangrokjung/claude-forge · 37 tokens

review-loop

Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…

sangrokjung/claude-forge · 100 tokens