用于处理 ClawSweeper 的巡检报告、修复任务、合并流程与运维监控。
整体看是低风险偏谨慎:材料显示它是开源 GitHub 技能,且无密钥、无声明远程端点,核心形态更像本地/仓库内自动化与报告生成。主要需要留意的是它会进行 GitHub App 相关操作与仓库读写,但这属于该类工具的常规能力。
未要求用户提供密钥或 token;README 仅提到 `CLAWSWEEPER_*` 配置与 GitHub App 私钥用于短期 App token 流程,未见额外凭证滥用迹象。
材料未声明任何外部远程端点或非 GitHub 的数据外发目标;可见的网络交互主要围绕 GitHub/GH 工作流与仓库操作。
它会在本机执行构建与脚本(如 `pnpm run build:all`、workflow/dispatch 流程),属于此类自动化技能的常规本地执行能力,未见超出描述目的的系统权限申请。
会访问仓库内容、提交报告与问题/PR 记录,可能读取本地工作区与 GitHub 相关数据;但材料未显示过度授权或超范围文件访问。
来源为 GitHub 开源仓库且社区星标很高,审计性与可信度较好;但许可证未声明、维护状态未知,供应链风险仍需按常规谨慎对待。
复制安装指令,让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "clawsweeper" 技能: 1. 下载 https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/clawsweeper/SKILL.md 2. 保存为 ~/.claude/skills/clawsweeper/SKILL.md 3. 装好后重载技能,告诉我可以用了
请为这个 OpenClaw 仓库执行一次 ClawSweeper 巡检,汇总 issue、PR 状态、失败检查项和待处理修复建议,并按优先级输出。
输出一份结构化巡检报告,包含问题概览、风险项和建议处理顺序。
请根据最新的 ClawSweeper 审查结果,对当前失败的 PR 执行可信自动修复;如果检查全部通过且满足门禁条件,则自动合并。
返回修复执行结果、变更摘要、门禁状态以及是否已自动合并。
请检查该仓库的 GitHub Actions 运行状态、权限配置和阻塞门禁,指出失败原因,并给出需要手动回填或维护者介入的步骤。
输出故障诊断、权限或门禁异常说明,以及可执行的修复步骤清单。
ClawSweeper lives at ~/Projects/clawsweeper. It is the one OpenClaw
maintenance bot for sweeping, commit review, repair jobs, and guarded fix PRs.
Use this skill whenever asked about reports, findings, dispatch health,
repair/cloud PR creation, comment commands, automerge, permissions, or gates.
cd ~/Projects/clawsweeper
git status --short --branch
git pull --ff-only
pnpm run build:all
Do not overwrite unrelated edits. If the tree is dirty, inspect first and keep read-only report work read-only unless the requester asked to commit.
Use the ClawSweeper repo and the clawsweeper GitHub App. Use only
CLAWSWEEPER_* configuration for this automation. Do not use legacy apps,
variables, labels, or skills.
Required app setup:
CLAWSWEEPER_APP_CLIENT_ID: public app client ID for clawsweeper.CLAWSWEEPER_APP_PRIVATE_KEY: private key used only inside
actions/create-github-app-token steps.openclaw/clawsweeper for comment-router
re-review dispatch, workflow dispatch, run cancellation, and self-heal;
optional Checks write for commit Check Runs.Token boundary:
Canonical commit reports:
records/<repo-slug>/commits/<40-char-sha>.md
Use the lister:
pnpm commit-reports -- --since 6h
pnpm commit-reports -- --since "24 hours ago" --findings
pnpm commit-reports -- --since 7d --non-clean
pnpm commit-reports -- --repo openclaw/openclaw --author steipete --since 7d
pnpm commit-reports -- --since 24h --json
Results: nothing_found, findings, inconclusive, failed,
skipped_non_code. One report per SHA; reruns overwrite the SHA-named report.
Manual rerun/backfill:
gh workflow run commit-review.yml --repo openclaw/clawsweeper \
-f target_repo=openclaw/openclaw \
-f commit_sha=<end-sha> \
-f before_sha=<start-or-parent-sha> \
-f create_checks=false \
-f enabled=true
Use create_checks=true only when the requester explicitly wants target commit Check
Runs. Add -f additional_prompt="..." for focused one-off review instructions.
Issue/PR reports live at:
records/<repo-slug>/items/<number>.md
records/<repo-slug>/closed/<number>.md
Lead with counts, concrete findings, and report links. Do not post unsolicited GitHub comments from report-reading work. Public surfaces are markdown reports, durable ClawSweeper review comments, and optional checks.
PR reports include Codex /review-style reviewFindings with priority,
confidence, repository-relative file, and line range. Public PR comments show a
short Review findings: list when findings exist; full review comments,
evidence links, likely owners, and runtime details stay inside the collapsed
Review details block.
Useful commands:
pnpm run status
pnpm run audit
pnpm run reconcile
pnpm run apply-decisions -- --dry-run
Create a job from issue/PR refs and a maintainer prompt:
pnpm run repair:create-job -- \
--repo openclaw/openclaw \
--refs 123,456 \
--prompt-file /tmp/clawsweeper-prompt.md
Create from an existing ClawSweeper report:
pnpm run repair:create-job -- \
--from-report ../clawsweeper/records/openclaw-openclaw/items/123.md
The job creator checks for an existing open PR, body match, or remote
clawsweeper/<cluster-id> branch before writing another job. Use --dry-run
to inspect. Use --force only after deciding the duplicate guard is stale.
Validate, commit, then dispatch:
…
用 songsee CLI 从音频生成频谱图与特征面板可视化,便于分析与展示。
连接 Discord 驱动的 OpenClaw 会话,直接与智能代理实时交流协作。
帮助维护者分诊、清理并解决 GitHub 中的 OpenClaw 密钥泄露告警。
帮助开发与运维团队快速分诊安全通告、草稿和 GHSA 报告并给出可信依据。
帮助定位 OpenClaw 测试中的内存增长、堆泄漏与 OOM 根因
基于问题或 PR 列表深度审查代码,只修复高确定性的小型 OpenClaw 缺陷。
帮助维护者高效审查、分诊并交接 ClawHub 的 GitHub 问题与 PR。
帮助团队在 GitHub Actions 中创建或更新受保护的实现 PR 并支持自动合并审查流程。
帮助维护者快速审查、分诊并处理 OpenClaw 的 Issue 与 PR。
帮助维护者检查、修复并验证 OpenClaw 的 GHSA 安全公告与私有分叉状态。
帮助开发与运维团队运行、排查并总结 OpenClaw 发布 CI 与发布前检查流程
帮助开发者批量定位并修复可合入的高置信小型 OpenClaw 缺陷