skills.rest
JEROME-PRAKASH-L
JEROME-PRAKASH-LCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openclaw-landable-bug-sweep

Finds and repairs five small non-SDK OpenClaw bugfix PRs until landable.

1|Updated Jun 9, 2026
Search Tags:#code review#pull request#github#triage#bugfix#ci#openclaw
One-click install
npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill openclaw-landable-bug-sweep-jerome-prakash-l
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-landable-bug-sweep
Source: https://github.com/JEROME-PRAKASH-L/openclaw/tree/main/.agents/skills/openclaw-landable-bug-sweep
Command: npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill openclaw-landable-bug-sweep-jerome-prakash-l

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers need a disciplined way to turn scattered OpenClaw issues and stale PRs 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, 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 low-risk bugfix PRs, each with proof commands, clean autoreview, and green CI. ## Quick Start Use $openclaw-landable-bug-sweep 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 OpenClaw bugfix PRs automatically?▼

Run the sweep loop: cluster open issues and PRs, prove the root cause in current code, patch with a regression test, rebase on main, run autoreview, push, and verify live CI is green. Repeat until exactly five PR URLs meet the bar.

What kinds of bugs qualify for this bug sweep?▼

Only small, proven runtime bugs qualify: production diffs under 500 LOC, no new dependencies or config, no backward-incompatible behavior, and a feasible focused test. Features, docs-only changes, and speculative reports are rejected.

Can this skill change the OpenClaw plugin SDK or public API?▼

No. Plugin SDK, public plugin API, and src/plugin-sdk boundary changes are explicitly rejected because they require separate architecture review. Auth and security boundary changes are also excluded unless explicitly assigned.

What happens to existing contributor PRs during the sweep?▼

Good PRs are rebased, fixed, autoreviewed, pushed, and counted once CI is green. Unwritable or poorly shaped PRs are recreated with contributor credit preserved, and duplicates or already-fixed items are closed with proof.

Why is a PR not counted even after local tests pass?▼

A PR only counts after its exact head is rebased on current main, passes autoreview with no actionable findings, is pushed, and shows green live GitHub CI. Pending, red, conflicting, or externally blocked PRs are excluded.

Related Skills

Explore More Software Engineering Skills→
steipetesteipete
388.4k

tag-duplicate-prs-issues

Detect duplicate OpenClaw pull requests and issues using gitcrawl and prtags.

Community
Advanced
AbildtoftAbildtoft
2

kramme:changelog-generator

Generate concise changelogs from GitHub PR merges into main.

Community
Intermediate
cogni-daocogni-dao
4

validate-candidate

Validate PR flight deployments against head SHA and Loki signals.

Official
Advanced
mkusakamkusaka
7

code-review-phase-3-sweep-for-gaps

Perform a final code review sweep to identify defects missed in earlier stages.

Community
Intermediate