openclaw pr maintainer

AI Community

Skill notes

Start issue and PR triage with gitcrawl

Use $gitcrawl first anytime you inspect OpenClaw issues or PRs. Check local gitcrawl data first for related threads, duplicate attempts, and already-landed fixes. Use gitcrawl for candidate discovery and clustering; use gh, gh api, and the current checkout to verify live state before commenting, labeling, closing, or landing. If gitcrawl is missing, stale, lacks the target thread, or has no embeddings for neighbor/search commands, fall back to the GitHub search workflow below.

Claim specific review targets

When a maintainer asks Codex to review, triage, fix, or land a specific OpenClaw issue/PR, check assignment before deep work. Identify the requesting maintainer's GitHub login. In this environment, default Peter to steipete; if another maintainer is clearly the requester, use that maintainer's bare login. Read current assignees with live gh issue view / gh pr view; gitcrawl is not enough for assignment state.

Surface opener identity

For every reviewed, triaged, closed, or landed issue/PR, show the opener's human name when available, GitHub login, and account age. Get the login from gh issue view / gh pr view (author.login), then fetch profile metadata once with gh api users/<login> --jq '{login,name,created_at,type}'. Report opener identity as one compact line: 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

Suppress top-maintainer items in issue triage

When asked for issue triage, hot issues, pressing bugs, Discord-correlated issues, or "what is still open", do not surface issues or PRs authored by top maintainers by default. Prefer external/user-reported hot issues and external PRs, not maintainer-owned work queues. Suppress by default when the opener/author is one of: @vincentkoc @Takhoffman @gumadeiras

Apply close and triage labels correctly

If an issue or PR matches an auto-close reason, apply the label and let .github/workflows/auto-response.yml handle the comment/close/lock flow. Do not manually close plus manually comment for these reasons. If an issue/PR is already fixed on current main or solved by a new release, comment with proof plus the canonical commit/PR/release, then close it. r:* labels can be used on both issues and PRs.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@yimmy23 · no license declared
Token usage
Heavy
Setup complexity
Manual integration
External API key
Not required
Operating systems
Windows · Docker
Runtime requirements
Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview openclaw-pr-maintainer.preview
# Structure PR review output

gh pr view <number> --json additions,deletions,changedFiles \
  --jq '"LOC: +\(.additions)/-\(.deletions) (\(.changedFiles) files)"'

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.