// Use when reviewing, triaging, validating, or discussing ClawHub GitHub issues or pull requests, including author context, CI, UI proof, evidence, labels, close decisions, and maintainer handoff.
Use when ClawHub needs Codex review, autoreview, second-model review, or a final advisory review gate before commit, PR update, ship, or maintainer handoff.
Use for ClawHub staff moderation actions with the repo-local clawhub-mod tool: unhide skills, ban or unban users, change roles, and verify moderation state.
Use when ClawHub UI changes need visual proof, before/after comparison, new-feature screenshots, temporary Playwright scenarios, or Crabbox desktop recordings.
Use when ClawHub needs remote Linux validation, CI-parity checks, broad Bun gates, hosted-service checks, desktop/VNC inspection, or Crabbox lease cleanup.
| name | clawhub-pr-maintainer |
| description | Use when reviewing, triaging, validating, or discussing ClawHub GitHub issues or pull requests, including author context, CI, UI proof, evidence, labels, close decisions, and maintainer handoff. |
Use this skill for maintainer-facing ClawHub GitHub workflow, not for ordinary implementation work.
gh pr view or gh issue view against openclaw/clawhub; verify live
state before commenting, labeling, closing, or recommending merge.Common read-only commands:
gh pr view <number> --repo openclaw/clawhub --json title,body,author,labels,comments,files,commits,statusCheckRollup,reviewDecision,url
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}'
proof:ui just to inspect
existing evidence.Use the clawhub-ui-proof skill when the maintainer/agent should generate new
visual evidence.
before-after: bug fixes, regressions, changed copy, changed layout, or any
PR where main-vs-candidate comparison clarifies the change.feature: new page, new flow, new UI state, or behavior that cannot exist on
origin/main.Write a temporary Playwright scenario under .artifacts/proof-scenarios/; do
not infer manual clicks. Keep screenshots and videos in .artifacts/ until
publishing. Never commit proof artifacts.
If this review generated proof:ui artifacts, publish them before the final PR
review comment. Do not leave only local .artifacts/... paths in a PR comment;
they are useful to the maintainer locally but invisible to GitHub readers.
Use:
bun run proof:publish -- --proof-dir .artifacts/clawhub-ui-proof/<timestamp> --target-pr <number>
proof:publish copies the selected files to the qa-artifacts branch and
upserts a marker-backed PR comment with a ClawHub UI Proof section.
That comment includes:
before-after or feature)report.md result summaryUse --dry-run before publishing if you need to inspect the generated comment.
If publishing fails because credentials are missing, report the local proof
directory and the failed command instead of posting a comment that claims
evidence is attached.
ClawSweeper is the bot control plane for automated PR/issue review once ClawHub dispatch is configured. Until then, use this skill for manual maintainer review. If ClawSweeper has posted a review, read it as evidence but verify live PR state before acting.
--body-file; never pass escaped
\n strings.gh pr comment --body-file is fine.
When proof artifacts were generated, use proof:publish so screenshots/videos
are published before posting.