# Clawhub PR Maintainer

Use when reviewing, triaging, validating, or discussing ClawHub GitHub issues or pull...

- Repository: https://github.com/openclaw/clawhub (9543 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add openclaw/clawhub --skill clawhub-pr-maintainer -g -a claude-code -y`
Codex: `npx skills add openclaw/clawhub --skill clawhub-pr-maintainer -g -a codex -y`
Cursor: `npx skills add openclaw/clawhub --skill clawhub-pr-maintainer -g -a cursor -y`
Gemini CLI: `npx skills add openclaw/clawhub --skill clawhub-pr-maintainer -g -a gemini-cli -y`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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:

```sh
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

The rest: https://github.com/openclaw/clawhub/blob/HEAD/.agents/skills/clawhub-pr-maintainer/SKILL.md