ClawHub PR Maintainer

Use this skill for maintainer-facing ClawHub GitHub workflow, not for ordinary implementation work.

Start With Live GitHub State

• Use gh pr view or gh issue view against openclaw/clawhub; verify live state before commenting, labeling, closing, or recommending merge.
• For PRs, read title, body, author, labels, comments, files, commits, status checks, review state, and linked issues.
• Surface author identity briefly: GitHub name/login and account age when useful. Treat identity as triage signal, never as proof by itself.

Common read-only commands:

gh pr view <number> --repo openclaw/clawhub --json title,body,author,labels,comments,files,commits,statusCheckRollup,reviewDecision,url,additions,deletions,changedFiles
gh issue view <number> --repo openclaw/clawhub --json title,body,author,labels,comments,state,url
gh api users/<login> --jq '{login,name,created_at,type}'

Review Evidence Bar

• For bug fixes, require symptom evidence, a plausible root cause in the touched code path, and either a regression test or focused manual proof.
• For UI changes, require screenshots or video when the behavior is meaningfully visual. Use tests as supplemental evidence, not a substitute for visible proof.
• Do not merge or recommend merge based only on PR prose, AI rationale, or green CI when the changed behavior has not been exercised.
• For contributor-provided screenshots/videos/logs, inspect the artifact directly and state what it proves. Do not rerun proof:ui just to inspect existing evidence.

Structure PR Review Output