帮助维护者快速审查、分诊并处理 OpenClaw 的 Issue 与 PR。
复制安装指令,让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "openclaw-pr-maintainer" 技能: 1. 下载 https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/openclaw-pr-maintainer/SKILL.md 2. 保存为 ~/.claude/skills/openclaw-pr-maintainer/SKILL.md 3. 装好后重载技能,告诉我可以用了
请检查这个 OpenClaw PR:https://github.com/.../pull/123 。总结变更内容、潜在风险、是否缺少测试,并给出是否建议合并的结论。
返回一份简明审查意见,包含变更摘要、风险点、测试情况与合并建议。
请处理这个 OpenClaw issue:#456。判断问题类型与优先级,搜索是否有重复 issue,并建议添加哪些 labels。
返回分诊结果,包括优先级、重复项链接、建议标签和后续处理建议。
请分析这个 PR 的提交者信息:#789。查看作者账号年龄、活跃度、过往贡献、评论记录,并评估是否需要维护者额外关注。
输出作者背景摘要与可信度判断,并说明是否存在可疑迹象或需要人工复核。
Use this skill for maintainer-facing GitHub workflow, not for ordinary code changes.
$gitcrawl first anytime you inspect OpenClaw issues or PRs.gitcrawl data first for related threads, duplicate attempts, and already-landed fixes.gitcrawl for candidate discovery and clustering; use gh, gh api, and the current checkout to verify live state before commenting, labeling, closing, or landing.gitcrawl is missing, stale, lacks the target thread, or has no embeddings for neighbor/search commands, fall back to the GitHub search workflow below.gitcrawl sync --include-comments, future enrichment commands, or broad reclustering unless the user asked to update the local store or stale data is blocking the decision.Common read-only path:
gitcrawl threads openclaw/openclaw --numbers <issue-or-pr-number> --include-closed --json
gitcrawl neighbors openclaw/openclaw --number <issue-or-pr-number> --limit 12 --json
gitcrawl search openclaw/openclaw --query "<scope or title keywords>" --mode hybrid --json
gitcrawl cluster-detail openclaw/openclaw --id <cluster-id> --member-limit 20 --body-chars 280 --json
When a maintainer asks Codex to review, triage, fix, or land a specific OpenClaw issue/PR, check assignment before deep work.
steipete; if another maintainer is clearly the requester, use that maintainer's bare login.gh issue view / gh pr view; gitcrawl is not enough for assignment state.assigned, time unknown; treat as assigned, not stale.Assignment time proof:
gh api "repos/openclaw/openclaw/issues/<number>/timeline" --paginate \
-H "Accept: application/vnd.github+json" \
--jq '[.[] | select(.event=="assigned") | {assignee:.assignee.login, assigner:.assigner.login, actor:.actor.login, created_at}]'
Use the newest assigned event for each current assignee. Issue timeline events expose created_at; GitHub GraphQL AssignedEvent.createdAt is also valid when REST pagination is awkward.
Claim command for issues or PRs:
gh api -X POST "repos/openclaw/openclaw/issues/<number>/assignees" -f 'assignees[]=<login>' >/dev/null
gh issue view / gh pr view (author.login), then fetch profile metadata once with gh api users/<login> --jq '{login,name,created_at,type}'.By: Jane Doe (@jane, acct 2021-04-03) | OpenClaw: 4 PRs, 2 issues, 11 commits/12mo | GitHub: 9 repos, 86 commits, 9 PRs, 3 issues, 12 reviews…
帮助团队检索重复的 PR 与问题单,并自动分组同步重复状态。