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, 왜 교체된 수장이나 홍보 기관이 새로운 증거가 필요한지, 그리고 왜 준비 태세가 합병 권한이 아닌가.

🦞🧹 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.