ClawSweeperはOpenClawリポジトリの保守的なレビューボットです。それは バックログはレビューされ、管理者が見えるGitHubコメントを整理し、適用されます 変わらない高信頼度の提案は決定論的セーフティゲートを通じて閉じられます。

ダッシュボードのWorkerの明示的な生産目標はopenclaw/openclawです。 openclaw/clawhub、openclaw/clawsweeper、およびopenclaw/fs-safe。追加 公開のopenclaw/*およびsteipete/*リポジトリは、設定済みプロファイルを使用することができます。 保守的なジェネリックのバックアップレビューはイベントディスパッチとスケジュールされたものを通じた ファンアウト。

プロジェクトのビジョンと境界線:VISION.md

タスクと対象者ごとの記録:docs/README.md

貢献

ローカルセットアップ、PR範囲、本文証明、著者所有レビューループについては、 プルを開いたり更新したりする前に、CONTRIBUTING.md を必ず読んでください リクエスト。ドキュメントインデックスを使ってアーキテクチャにアクセスし、 構成、ダッシュボード、ポリシー、オペレーター参照をスキャンせずに閲覧できます README全体。貢献ガイドには、いつ使用すべきかが説明されています @clawsweeper re-review、交代したトップやPR機関が新たな証拠を必要とする理由、 そして、なぜ準備が統合権限ではないのか。

🦞🧹 ClawSweeper

ClawSweeper is the conservative review bot for OpenClaw repositories. It keeps the backlog reviewed, keeps maintainer-visible GitHub comments tidy, and applies unchanged, high-confidence close proposals through deterministic safety gates.

The dashboard Worker’s explicit production targets are openclaw/openclaw, openclaw/clawhub, openclaw/clawsweeper, and openclaw/fs-safe. Additional public openclaw/* and steipete/* repositories can use configured profiles or conservative generic fallback review through event dispatch and scheduled fanout.

Project vision and boundaries: VISION.md

Documentation by task and audience: docs/README.md

Contributing

For local setup, PR scope, main-body proof, and the author-owned review loop, read CONTRIBUTING.md before opening or updating a pull request. Use the documentation index to reach architecture, configuration, dashboard, policy, and operator references without scanning this entire README. The contributing guide explains when to use @clawsweeper re-review, why a changed head or PR body needs fresh evidence, and why readiness is not merge authority.

The OpenClaw-hosted ClawSweeper instance is not a public review service and does not provide free reviews for third-party repositories. If you want ClawSweeper for your own project, fork this repository, deploy it in your own organization, and configure that self-hosted instance for your repositories.

At a high level ClawSweeper:

• reviews open issues and pull requests on a schedule and on exact GitHub events
• writes one durable markdown report per item in generated state
• syncs one marker-backed public review comment per issue or PR, edited in place
• closes only unchanged, high-confidence, policy-allowed proposals
• routes maintainer commands @clawsweeper review, @clawsweeper re-review, @clawsweeper explain, and @clawsweeper stop
• can acknowledge maintainer comment commands through an optional GitHub App webhook before the GitHub Actions fallback starts
• can review local branch ranges with repository and GitHub access kept local while Codex connects to the configured model service
• publishes canonical review records to the Cloudflare Worker, action ledgers and assets to R2, and the remaining operational state to openclaw/clawsweeper-state

The oversized PR close lane proposes closing pull requests above 50,000 changed lines before hydration, scanning, or model review, with a maintainer size: accepted-large exemption. See the close-policy index for the guarded close lanes.

ClawSweeper is not a generic auto-close bot. Review is proposal-only, apply is guarded, Codex never gets write credentials during review, and every GitHub mutation is rechecked against live target state immediately before it happens.