$ ~/registry/skill/openclaw-agents-skills-openclaw-small-bugfix-sweep

SKILL

openclaw-small-bugfix-sweep

Name: openclaw-small-bugfix-sweep
Author: openclaw

Deeply review code and fix only small, high-confidence OpenClaw bugs.

Stars

★ 382,582

Source

GitHub

Updated

2026-07-11

// securityLow risk

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

Summary

The material indicates a prompt-only workflow with no required secrets and no declared remote endpoints, so overall risk is low. While the README mentions using tools like gh and gitcrawl to read live targets, the provided materials and system checks do not show concrete high-risk red flags.

CredentialsLow risk

Both the material and system checks state that no keys or environment variables are required. No tokens, accounts, or other sensitive credentials are requested, so credential exposure risk appears low.

Network egressLow risk

The system lists no remote endpoints, and the skill is classified as prompt-only. Although the README mentions using gh to read live targets, the material does not declare any built-in outbound endpoint or explicit data-upload behavior for this skill.

Code executionLow risk

As a prompt-only skill, the current material does not show that it itself can spawn local processes, execute scripts, or invoke system capabilities. The README's 'Execute' wording appears to be workflow instruction rather than auditable execution capability.

Data accessLow risk

No filesystem, database, or system-resource permissions are declared. The README only describes a code-review and local-fix workflow, with no evidence in the material that it has actual data read/write capability beyond a normal prompt.

Supply chainLow risk

The source is an open GitHub repository, the system marks it as open-source, and community adoption is very high (about 377k stars), all of which are strong risk-reducing signals. The missing license declaration and unknown maintenance status are gaps, but not enough on their own to raise it to high risk.

Recommendations

Still use it in an isolated environment and verify whether it invokes external tools such as gh or gitcrawl.
If later versions introduce network endpoints, automatic commit/push behavior, or credential requirements, reassess the security posture.
Before actual use, check recent maintenance activity, release history, and dependency changes in the repository.

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

// install

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

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

// download

Download SKILL.mdInstall manifest ↗

// examples

Triage and fix small bugs

Prompt

Here is a list of issues/PRs for the OpenClaw project. First perform a deep code review, then only fix items that are small in scope, low risk, and have a clear solution. Skip anything requiring refactors, unclear requirements, or broad impact. Output the reason, change summary, and patch suggestion for each fixed item. List:

Expected

Returns vetted small-bug fixes, explains skipped items, and provides applicable patch content.

Review minor safety issues in PRs

Prompt

Review this set of OpenClaw PRs and look for high-certainty small issues such as null handling, boundary checks, and missing error handling. Only propose fixes when they do not change core behavior, and list suggested diffs by file. PR list:

Expected

Outputs precise file-by-file fixes focused on safe, conservative small changes.

Prepare a small-fix list for a maintenance branch

Prompt

I need small bug fixes for an OpenClaw maintenance branch. Based on the issue list below and the related code, keep only fixes that can be committed independently, are easy to verify, and have low regression risk. Also draft commit messages. Issue list:

Expected

Generates a maintenance-branch-ready fix list, patch suggestions, and concise commit messages.

// docs

OpenClaw Small Bugfix Sweep

Batch workflow for pasted OpenClaw issue/PR refs. Execute, do not summarize. Triage reviews, proves, and patches local fixes first; publishing waits for Peter's manual review.

Peter Review Gate

Peter always wants to review code before commits. Default flow:

Review each issue deeply enough to prove current behavior and root cause.
Fix only easy, high-confidence bugs with narrow ownership and focused proof.
Stop with the dirty diff summary, touched files, and test/gate output for Peter's manual review.
After Peter approves shipping, make one commit per accepted fix, with a changelog entry for each user-facing fix.
Pull/rebase, push, then comment and close only the fixed or explicitly triaged-closed issues.

Do not batch unrelated issue fixes into one commit. Do not push, create PRs, comment, close, label, land, merge, or otherwise publish during the review/prove phase.

Companion Skills

Use $gitcrawl first, $openclaw-pr-maintainer for live GitHub hygiene, $github-deep-review posture for source tracing, and $openclaw-testing for proof.

Loop

For each ref:

Read live target with gh.
Check gitcrawl for related, duplicate, closed, or already-fixed threads.
Read body, comments, linked refs, changed files, current code, adjacent tests, and dependency contracts when relevant.
Trace the real runtime path.
For issues: fix locally only if this is a bug, current code proves root cause, the implicated path is clear, and a narrow patch is cleaner than refactor.
For PRs: decide ready-to-merge, needs-fixup, or skip; do not alter PR branches unless explicitly asked.
Add focused regression proof when practical for local issue fixes or PR readiness checks.
Run the smallest meaningful gate.
Continue until every pasted ref is fixed or classified.

No subagents unless explicitly requested.

Skip If

not a bug
config/docs/workflow/release/support/dependency/product work
repro or root cause is uncertain
larger refactor or owner-boundary change is cleaner
already fixed on current main
dependency behavior is guessed
no focused proof is feasible

Skip with terse reason. Do not pad with low-confidence fixes.

Fix Rules

owner module first; generic seam only when required
existing patterns/helpers/types
no drive-by refactors
tests near failing surface
docs only for changed public behavior
no commit during the review/prove phase
after Peter approves shipping, one commit plus changelog per accepted user-facing fix
no push/create PR/comment/close/label/land/merge until Peter approves shipping after review

PR Rules

ready-to-merge: code is good, current head checked, required proof is green or clearly pending only external CI; list for maintainer merge or @clawsweeper automerge
needs-fixup: small bug is clear, but PR branch needs changes; list exact files/tests and wait for explicit fix/push/automerge instruction
skip: broad, stale, speculative, config/product/security/release, owner-boundary, or refactor-sized
if source PR is untrusted/uneditable, do not create a replacement PR during sweep

Output Shape

Ledger: fixed-local, ready-to-merge, needs-fixup, skipped, needs-human. Final: issue files left on disk, PRs ready for merge/automerge, tests/gates, skip reasons.

Handle ClawSweeper reports, fixes, merges, permissions, and GitHub workflow monitoring.

openclawGet→

$ loading_