[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openclaw-openclaw-.agents-skills-openclaw-pr-maintainer":3},{"error":4,"detail":5,"metadata":23,"markdownContent":24,"rawMarkdown":20},false,{"repo_full_name":6,"owner":7,"repo_name":7,"repo_forks":8,"skill_path":9,"repo_stars":10,"name":11,"category_id":12,"description":13,"file_tree":14,"skill_md_content":20,"skill_id":21,"skill_key":22},"openclaw/openclaw","openclaw",62380,".agents/skills/openclaw-pr-maintainer",323646,"openclaw-pr-maintainer",1,"Maintainer workflow for reviewing, triaging, preparing, closing, or landing OpenClaw pull requests and related issues. Use when Codex needs to validate bug-fix claims, search for related issues or PRs, apply or recommend close/reason labels, prepare GitHub comments safely, check review-thread follow-up, or perform maintainer-style PR decision making before merge or closure.",[15],{"name":16,"path":17,"size":18,"type":19},"SKILL.md",".agents/skills/openclaw-pr-maintainer/SKILL.md",3867,"file","---\nname: openclaw-pr-maintainer\ndescription: Maintainer workflow for reviewing, triaging, preparing, closing, or landing OpenClaw pull requests and related issues. Use when Codex needs to validate bug-fix claims, search for related issues or PRs, apply or recommend close/reason labels, prepare GitHub comments safely, check review-thread follow-up, or perform maintainer-style PR decision making before merge or closure.\n---\n\n# OpenClaw PR Maintainer\n\nUse this skill for maintainer-facing GitHub workflow, not for ordinary code changes.\n\n## Apply close and triage labels correctly\n\n- 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.\n- Do not manually close plus manually comment for these reasons.\n- `r:*` labels can be used on both issues and PRs.\n- Current reasons:\n  - `r: skill`\n  - `r: support`\n  - `r: no-ci-pr`\n  - `r: too-many-prs`\n  - `r: testflight`\n  - `r: third-party-extension`\n  - `r: moltbook`\n  - `r: spam`\n  - `invalid`\n  - `dirty` for PRs only\n\n## Enforce the bug-fix evidence bar\n\n- Never merge a bug-fix PR based only on issue text, PR text, or AI rationale.\n- Before landing, require:\n  1. symptom evidence such as a repro, logs, or a failing test\n  2. a verified root cause in code with file/line\n  3. a fix that touches the implicated code path\n  4. a regression test when feasible, or explicit manual verification plus a reason no test was added\n- If the claim is unsubstantiated or likely wrong, request evidence or changes instead of merging.\n- If the linked issue appears outdated or incorrect, correct triage first. Do not merge a speculative fix.\n\n## Handle GitHub text safely\n\n- For issue comments and PR comments, use literal multiline strings or `-F - \u003C\u003C'EOF'` for real newlines. Never embed `\\n`.\n- Do not use `gh issue/pr comment -b \"...\"` when the body contains backticks or shell characters. Prefer a single-quoted heredoc.\n- Do not wrap issue or PR refs like `#24643` in backticks when you want auto-linking.\n- PR landing comments should include clickable full commit links for landed and source SHAs when present.\n\n## Search broadly before deciding\n\n- Prefer targeted keyword search before proposing new work or closing something as duplicate.\n- Use `--repo openclaw/openclaw` with `--match title,body` first.\n- Add `--match comments` when triaging follow-up discussion.\n- Do not stop at the first 500 results when the task requires a full search.\n\nExamples:\n\n```bash\ngh search prs --repo openclaw/openclaw --match title,body --limit 50 -- \"auto-update\"\ngh search issues --repo openclaw/openclaw --match title,body --limit 50 -- \"auto-update\"\ngh search issues --repo openclaw/openclaw --match title,body --limit 50 \\\n  --json number,title,state,url,updatedAt -- \"auto update\" \\\n  --jq '.[] | \"\\(.number) | \\(.state) | \\(.title) | \\(.url)\"'\n```\n\n## Follow PR review and landing hygiene\n\n- If bot review conversations exist on your PR, address them and resolve them yourself once fixed.\n- Leave a review conversation unresolved only when reviewer or maintainer judgment is still needed.\n- When landing or merging any PR, follow the global `/landpr` process.\n- Use `scripts/committer \"\u003Cmsg>\" \u003Cfile...>` for scoped commits instead of manual `git add` and `git commit`.\n- Keep commit messages concise and action-oriented.\n- Group related changes; avoid bundling unrelated refactors.\n- Use `.github/pull_request_template.md` for PR submissions and `.github/ISSUE_TEMPLATE/` for issues.\n\n## Extra safety\n\n- If a close or reopen action would affect more than 5 PRs, ask for explicit confirmation with the exact count and target query first.\n- `sync` means: if the tree is dirty, commit all changes with a sensible Conventional Commit message, then `git pull --rebase`, then `git push`. Stop if rebase conflicts cannot be resolved safely.\n","f72babe4-4301-5d15-b9e2-57cc031f6b05","openclaw-openclaw-.agents-skills-openclaw-pr-maintainer",{"name":11,"description":13},"\u003Ch1>OpenClaw PR Maintainer\u003C/h1>\n\u003Cp>Use this skill for maintainer-facing GitHub workflow, not for ordinary code changes.\u003C/p>\n\u003Ch2>Apply close and triage labels correctly\u003C/h2>\n\u003Cul>\n\u003Cli>If an issue or PR matches an auto-close reason, apply the label and let \u003Ccode>.github/workflows/auto-response.yml\u003C/code> handle the comment/close/lock flow.\u003C/li>\n\u003Cli>Do not manually close plus manually comment for these reasons.\u003C/li>\n\u003Cli>\u003Ccode>r:*\u003C/code> labels can be used on both issues and PRs.\u003C/li>\n\u003Cli>Current reasons:\u003Cul>\n\u003Cli>\u003Ccode>r: skill\u003C/code>\u003C/li>\n\u003Cli>\u003Ccode>r: support\u003C/code>\u003C/li>\n\u003Cli>\u003Ccode>r: no-ci-pr\u003C/code>\u003C/li>\n\u003Cli>\u003Ccode>r: too-many-prs\u003C/code>\u003C/li>\n\u003Cli>\u003Ccode>r: testflight\u003C/code>\u003C/li>\n\u003Cli>\u003Ccode>r: third-party-extension\u003C/code>\u003C/li>\n\u003Cli>\u003Ccode>r: moltbook\u003C/code>\u003C/li>\n\u003Cli>\u003Ccode>r: spam\u003C/code>\u003C/li>\n\u003Cli>\u003Ccode>invalid\u003C/code>\u003C/li>\n\u003Cli>\u003Ccode>dirty\u003C/code> for PRs only\u003C/li>\n\u003C/ul>\n\u003C/li>\n\u003C/ul>\n\u003Ch2>Enforce the bug-fix evidence bar\u003C/h2>\n\u003Cul>\n\u003Cli>Never merge a bug-fix PR based only on issue text, PR text, or AI rationale.\u003C/li>\n\u003Cli>Before landing, require:\u003Col>\n\u003Cli>symptom evidence such as a repro, logs, or a failing test\u003C/li>\n\u003Cli>a verified root cause in code with file/line\u003C/li>\n\u003Cli>a fix that touches the implicated code path\u003C/li>\n\u003Cli>a regression test when feasible, or explicit manual verification plus a reason no test was added\u003C/li>\n\u003C/ol>\n\u003C/li>\n\u003Cli>If the claim is unsubstantiated or likely wrong, request evidence or changes instead of merging.\u003C/li>\n\u003Cli>If the linked issue appears outdated or incorrect, correct triage first. Do not merge a speculative fix.\u003C/li>\n\u003C/ul>\n\u003Ch2>Handle GitHub text safely\u003C/h2>\n\u003Cul>\n\u003Cli>For issue comments and PR comments, use literal multiline strings or \u003Ccode>-F - <<'EOF'\u003C/code> for real newlines. Never embed \u003Ccode>\\n\u003C/code>.\u003C/li>\n\u003Cli>Do not use \u003Ccode>gh issue/pr comment -b "..."\u003C/code> when the body contains backticks or shell characters. Prefer a single-quoted heredoc.\u003C/li>\n\u003Cli>Do not wrap issue or PR refs like \u003Ccode>#24643\u003C/code> in backticks when you want auto-linking.\u003C/li>\n\u003Cli>PR landing comments should include clickable full commit links for landed and source SHAs when present.\u003C/li>\n\u003C/ul>\n\u003Ch2>Search broadly before deciding\u003C/h2>\n\u003Cul>\n\u003Cli>Prefer targeted keyword search before proposing new work or closing something as duplicate.\u003C/li>\n\u003Cli>Use \u003Ccode>--repo openclaw/openclaw\u003C/code> with \u003Ccode>--match title,body\u003C/code> first.\u003C/li>\n\u003Cli>Add \u003Ccode>--match comments\u003C/code> when triaging follow-up discussion.\u003C/li>\n\u003Cli>Do not stop at the first 500 results when the task requires a full search.\u003C/li>\n\u003C/ul>\n\u003Cp>Examples:\u003C/p>\n\u003Cdiv class=\"md-code-block\">\u003Cdiv class=\"md-code-lang\">bash\u003C/div>\u003Cpre>\u003Ccode class=\"hljs language-bash\">gh search prs --repo openclaw/openclaw --match title,body --\u003Cspan class=\"hljs-built_in\">limit\u003C/span> 50 -- \u003Cspan class=\"hljs-string\">"auto-update"\u003C/span>\ngh search issues --repo openclaw/openclaw --match title,body --\u003Cspan class=\"hljs-built_in\">limit\u003C/span> 50 -- \u003Cspan class=\"hljs-string\">"auto-update"\u003C/span>\ngh search issues --repo openclaw/openclaw --match title,body --\u003Cspan class=\"hljs-built_in\">limit\u003C/span> 50 \\\n  --json number,title,state,url,updatedAt -- \u003Cspan class=\"hljs-string\">"auto update"\u003C/span> \\\n  --jq \u003Cspan class=\"hljs-string\">'.[] | "\\(.number) | \\(.state) | \\(.title) | \\(.url)"'\u003C/span>\u003C/code>\u003C/pre>\u003C/div>\u003Ch2>Follow PR review and landing hygiene\u003C/h2>\n\u003Cul>\n\u003Cli>If bot review conversations exist on your PR, address them and resolve them yourself once fixed.\u003C/li>\n\u003Cli>Leave a review conversation unresolved only when reviewer or maintainer judgment is still needed.\u003C/li>\n\u003Cli>When landing or merging any PR, follow the global \u003Ccode>/landpr\u003C/code> process.\u003C/li>\n\u003Cli>Use \u003Ccode>scripts/committer "<msg>" <file...>\u003C/code> for scoped commits instead of manual \u003Ccode>git add\u003C/code> and \u003Ccode>git commit\u003C/code>.\u003C/li>\n\u003Cli>Keep commit messages concise and action-oriented.\u003C/li>\n\u003Cli>Group related changes; avoid bundling unrelated refactors.\u003C/li>\n\u003Cli>Use \u003Ccode>.github/pull_request_template.md\u003C/code> for PR submissions and \u003Ccode>.github/ISSUE_TEMPLATE/\u003C/code> for issues.\u003C/li>\n\u003C/ul>\n\u003Ch2>Extra safety\u003C/h2>\n\u003Cul>\n\u003Cli>If a close or reopen action would affect more than 5 PRs, ask for explicit confirmation with the exact count and target query first.\u003C/li>\n\u003Cli>\u003Ccode>sync\u003C/code> means: if the tree is dirty, commit all changes with a sensible Conventional Commit message, then \u003Ccode>git pull --rebase\u003C/code>, then \u003Ccode>git push\u003C/code>. Stop if rebase conflicts cannot be resolved safely.\u003C/li>\n\u003C/ul>\n"]