OpenClaw PR Maintainer

Use this skill for maintainer-facing GitHub workflow, not for ordinary code changes.

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.
• Do not run expensive/update commands such as 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: