openclaw/clawsweeper

ClawSweeper scans all issues and PRs and suggest what we can close, and why. It runs every PR / Issue once a week.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 59 minutes ago
Added to GitGenius on April 28th, 2026
Created on April 23rd, 2026
Open Issues & Pull Requests: 14 (-1)
Number of forks: 291
Total Stargazers: 1,963 (+0)
Total Subscribers: 9 (+0)

Issue Activity (beta)

Open issues: 4
New in 7 days: 10
Closed in 7 days: 10
Avg open age: 2 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

Opened in 7 days: 9
Closed in 7 days: 10
Comments in 7 days: 14
Events in 7 days: 95

Top labels

  • clawsweeper:no-new-fix-pr (58)
  • impact:other (55)
  • clawsweeper:source-repro (40)
  • issue-rating: 🦞 diamond lobster (40)
  • P2 (31)
  • clawsweeper:fix-shape-clear (31)
  • clawsweeper:needs-product-decision (30)
  • clawsweeper:linked-pr-open (29)

Repository Insights (GitGenius)

Median issue/PR response: 5.9 hours
Mean response time: 46.7 hours
90th percentile: 5.5 days
Tracked items: 110

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 7% of issues opened in the past year have been closed. Three people close 80% of everything that gets resolved.

Detailed Description

ClawSweeper is a maintenance bot designed specifically for OpenClaw repositories that automates the review and management of issues and pull requests. Written in TypeScript, it scans open issues and PRs on a scheduled basis and through exact GitHub events to propose which items can be safely closed and why. The bot runs reviews on every PR and issue once a week, maintaining a conservative approach to automation by keeping proposals separate from enforcement and requiring explicit maintainer approval before taking action.

The bot's primary targets are openclaw/openclaw, openclaw/clawhub, and its own repository for self-review. ClawSweeper is not positioned as a public review service and does not provide free reviews for third-party repositories. Users who want to use ClawSweeper for their own projects must fork the repository, deploy it within their own organization, and configure it for their specific repositories.

At its core, ClawSweeper performs several interconnected functions. It reviews open issues and pull requests on a schedule and in response to exact GitHub events, writing one durable markdown report per item in generated state. The bot syncs one marker-backed public review comment per issue or PR, editing it in place rather than posting repeated comments. It closes only unchanged, high-confidence, policy-allowed proposals and routes maintainer commands such as @clawsweeper review, @clawsweeper fix, @clawsweeper autofix, and @clawsweeper automerge. The bot can repair opted-in PRs through a bounded Codex review and fix loop before merge, automatically open guarded implementation PRs for viable reviewed issues in eligible public repositories, and manually review selected code-bearing commits on target main branches.

The review process is deliberately conservative. Maintainer-authored items stay open unless ClawSweeper can verify the request is already implemented on current main. Issues with open PRs that reference them using GitHub closing syntax remain open until that PR merges, is closed, or ClawSweeper closes that PR candidate.

Repository-specific rules live in src/repository-profiles.ts, allowing OpenClaw, ClawHub, and ClawSweeper to share the same engine while maintaining different apply limits for each project. Generated state is published to openclaw/clawsweeper-state on the state branch, containing durable records, jobs, results, audit output, workflow status, repair ledgers, and the rendered dashboard.

clawsweeper
by
openclawopenclaw/clawsweeper

Repository Details

Fetching additional details & charts...