openclaw-landable-bug-sweep

Find and repair five small non-SDK OpenClaw bugfix PRs until landable.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/AmirulAndalib/Vilvona-AI --skill openclaw-landable-bug-sweep-amirulandalib
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-landable-bug-sweep
Source: https://github.com/AmirulAndalib/Vilvona-AI/tree/main/.agents/skills/openclaw-landable-bug-sweep
Command: npx skills add https://github.com/AmirulAndalib/Vilvona-AI --skill openclaw-landable-bug-sweep-amirulandalib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of the OpenClaw repository need a disciplined way to turn scattered issues and stale pull requests into a small set of verified, merge-ready bugfix PRs without touching risky SDK or architecture boundaries. ## Core Features & Use Cases - Candidate triage: Clusters open issues and PRs, proves root causes in current code, and rejects features, SDK-boundary changes, and speculative reports. - Repair and publish loop: Rebases branches on current main, adds regression tests, runs autoreview, pushes the exact reviewed head, and verifies live GitHub CI is green. - Hygiene and ledger: Closes duplicates and already-fixed issues with proof, preserves contributor credit, and maintains an accepted/rejected/closed ledger ending in exactly five PR URLs. - Use Case: A maintainer asks the agent to sweep the OpenClaw tracker and return five landable bugfix PRs, each with proof commands, clean autoreview, and green CI. ## Quick Start Ask the agent to use the openclaw-landable-bug-sweep skill to find or repair five small high-confidence non-SDK-boundary OpenClaw bugfix PRs and get them landable.

Frequently Asked Questions about openclaw-landable-bug-sweep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I produce landable bugfix PRs for OpenClaw?

Run the sweep loop: cluster open issues and PRs, prove the root cause in current code, patch with a focused diff, rebase on main, run autoreview until clean, push the exact head, and verify live GitHub CI is green before counting the PR.

What kinds of bugs qualify for the OpenClaw bug sweep?

Only small, provable runtime bugs or paper cuts qualify, with production diffs well under 500 LOC, no new dependencies or config, and no backward-incompatible behavior. Features, docs-only changes, and speculative reports are rejected.

Can this sweep change the OpenClaw plugin SDK or public API?

No. Plugin SDK, public plugin API, and src/plugin-sdk boundary changes are explicitly excluded, including compatibility shims and new SDK exports. Those require separate architecture review outside this workflow.

What proof is required before a PR counts as landable?

Each PR needs a rebased head on current main, a focused local or live test proving the fix, a clean autoreview on the exact head, and green GitHub CI on the pushed commit. Pending, red, or conflicting PRs do not count.

What happens to duplicate or already-fixed issues during the sweep?

Duplicates and issues already fixed on main are closed with kind comments containing proof such as commit or PR links. Contributor credit is preserved when recreating or repairing existing pull requests.