[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698RCPEWQER76FBMJ56WB7H":3,"skill-same:01M698RCPEWQER76FBMJ56WB7H":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":46,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M698RCPEWQER76FBMJ56WB7H","openclaw-repair-sweep",null,"Run scoped OpenClaw issue\u002FPR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.","openclaw\u002Fopenclaw","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698PDMDRVH56MV30D253NFP",394302,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-repair-sweep\u002FSKILL.md",[],[18,9,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"openclaw repair sweep","sweep","repair","prove","scoped","authority","verified","root","close","pr repair","campaigns","coordinate","issue","workers","work","land","run","pr","2026-11-10 10:12:30",false,"---\nname: openclaw-repair-sweep\ndescription: \"Run scoped OpenClaw issue\u002FPR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.\"\n---\n\n# OpenClaw Repair Sweep\n\nUse for a multi-item repair campaign. Root `AGENTS.md` owns repair and safety\npolicy; `$openclaw-pr-maintainer` owns item review, GitHub writes, and landing.\nThe lead remains hands-on and delegates independent work where useful.\n\n## Scope and authority\n\n- Explicit refs imply a bounded ref campaign. Otherwise discovery defaults to\n  five qualified items (maximum twenty per batch); a whole-queue request means\n  continuing through that queue. Do not pad low-confidence findings.\n- Honor requested workers and focus. Ref\u002Fdiscovery campaigns normally use up to\n  eight item owners; a queue campaign can assign up to sixty-four, but actual\n  active proof workers must fit host\u002Fremote capacity. Start small and scale on\n  observed resource health; assigned is not the same as running.\n- An explicit autonomous fix-and-land\u002Fsweep invocation covers scoped investigation,\n  repairs, commits, pushes, PRs, verified landings and proven closures. Review,\n  triage, or list wording stays read-only; fix-only stops before publication.\n  Never infer release, schema\u002Fconfig\u002Fprotocol, credential, security, or product\n  approval from campaign authority.\n\nUse `$gitcrawl` for available archive discovery, `$openclaw-testing` for proof,\n`$autoreview` for independent code review, and `$crabbox` when the proof requires\nremote environment or untrusted-source isolation. Author-history research is\nconditional on a concrete question, not a campaign prerequisite.\n\n## Coordinate ownership\n\nAssign each item or shared root-cause cluster one owner, a checkout, frozen\nsource SHA, authorized actions, and a useful stopping condition. Duplicate\nsymptoms share an owner; repeated defect classes should be repaired in the\ncanonical owner rather than by parallel near-identical patches.\n\nUse isolated issue\u002FPR worktrees and preserve unrelated files. Serialize shared\nfetch\u002Fref\u002Fbranch\u002Fworktree operations, PR preparation, and merges in short slots;\nnever hold the slot across coding, tests, or a remote wait. Each remote lease has\none owner and one active command. Pause only campaign-owned work under resource\npressure, and preserve patches, claims, proof, and checkpoints before replacement.\nThe lead may take over stalled work safely; it is not an orchestration-only role.\n\nRead root and scoped guides before acting. Each verdict-bearing worker inspects\nits relevant dependency contracts directly, including the root's personal Codex\nsource requirement. The lead verifies consequential results, not just summaries.\nUse independent challenge for nontrivial repairs and closure evidence; one\nindependent autoreview is enough for the code-review requirement.\n\n## Investigate and repair\n\nSearch existing work before creating another fix: current body\u002Fcomments, related\narchive results, live state when it matters, and current source\u002Fhistory. Use bare\nPATH `gh` with narrow JSON fields; reuse shared evidence and avoid unnecessary\npagination or repeated item fetches.\n\nPrefer, in order:\n\n1. Prove the original behavior is already fixed on current main and close under\n   the authorized scope with the canonical fix and evidence.\n2. Finish and verify an existing useful editable PR, preserving human credit.\n3. If that PR cannot safely be updated, create a credited replacement before\n   closing it. Do not squash a contributor PR after replacing its ancestry.\n4. Implement a new high-confidence repair when no suitable fix exists.\n5. Record a concrete blocker or product\u002Fowner decision. A useful independent\n   simplification may land under its own scope, but it does not close the bug.\n\nA candidate needs a demonstrated current defect, an understood owner and\nbounded impact, relevant dependency proof, and feasible validation. Repairs\nrequiring new dependencies\u002Fconfiguration, public-contract changes, security,\npersistence design, or product judgment require their root approvals before\nimplementation or landing as applicable. Preserve useful investigation; do not\nwork around the gate or count review-required work as an accepted fix.\n\nRepair the invariant at its owner, cover relevant siblings, and remove connected\nobsolete paths when justified. Do not add speculative fallback layers or hardcode\nthe reported example. Prefer simplicity without a LOC quota. Keep release-note\ncontext and credit in the PR; `CHANGELOG.md` remains release-owned. Do not force a\nsecond refactor PR after each completed item.\n\n## Proof and landing\n\nChoose proportional proof through `$openclaw-testing`. Trusted development can\nrun locally; remote compute needs an environment or isolation reason. Untrusted\nrepository tooling never runs locally or on a credential-hydrated host. Preserve\nexplicit live requirements and never describe a mock, skipped test, old head, or\nunfinished soak as live proof.\n\nRun `$autoreview` on the completed nontrivial candidate and resolve verified\nfindings. Re-review substantive changes or unresolved concerns; do not multiply\nreviews for mechanical head movement. Address actionable human\u002Fbot findings\nwithout a separate Rank-up checklist or score-refresh gate.\n\nLand through the native maintainer workflow only with current required CI and\nreview evidence. Verify remote merge state and ancestry before counting success.\nA timed-out merge request may have succeeded; reconcile it before retrying.\nRefresh\u002Frebase for conflicts, failed guards, explicit requests, or material stale\nbase risk, not merely because main advanced. Delete only owned temporary state.\n\nFor broad campaigns, a shared-main failure may justify one separately scoped\nrepair worker. Check for an existing fix first. Do not duplicate that repair in\nevery PR or silently expand a bounded ref request to unrelated CI work.\n\n## Closure and reporting\n\nBefore closing, prove the reporter's primary outcome and affected surfaces are\nfixed, not merely mitigated or diagnosed. Check fix ancestry and containing tags\nwhen version claims matter; dates do not prove inclusion. Seek independent\nchallenge for uncertain or consequential closure evidence. Disagreement, a still\nbroken surface, or an owner hold means leave open. Product rejection is a\nmaintainer decision, never an automatic cleanup conclusion.\n\nRecheck live state before mutation and explain the fixed behavior, canonical\ncommit\u002FPR, known containing version, and useful proof. If a closure is challenged,\npause the affected closure work and correct the evidence before resuming. No more\nthan three workers should hold simultaneous closure duty; more than fifty\nclose\u002Freopen actions require the root's explicit count\u002Fscope approval.\n\nKeep a resumable ledger of owner, source\u002Fhead, outcome, proof\u002FCI state, PR\u002Fmerge,\ncredit, blockers, and cleanup. Count verified outcomes, not planned or launched\nwork. Report meaningful progress and each verified landing with links; summarize\nfinal behavior, proof, remaining limitations, and checkout state in natural prose.\n","# OpenClaw Repair Sweep\n\nUse for a multi-item repair campaign. Root `AGENTS.md` owns repair and safety\npolicy; `$openclaw-pr-maintainer` owns item review, GitHub writes, and landing.\nThe lead remains hands-on and delegates independent work where useful.\n\n## Scope and authority\n\n- Explicit refs imply a bounded ref campaign. Otherwise discovery defaults to\n  five qualified items (maximum twenty per batch); a whole-queue request means\n  continuing through that queue. Do not pad low-confidence findings.\n- Honor requested workers and focus. Ref\u002Fdiscovery campaigns normally use up to\n  eight item owners; a queue campaign can assign up to sixty-four, but actual\n  active proof workers must fit host\u002Fremote capacity. Start small and scale on\n  observed resource health; assigned is not the same as running.\n- An explicit autonomous fix-and-land\u002Fsweep invocation covers scoped investigation,\n  repairs, commits, pushes, PRs, verified landings and proven closures. Review,\n  triage, or list wording stays read-only; fix-only stops before publication.\n  Never infer release, schema\u002Fconfig\u002Fprotocol, credential, security, or product\n  approval from campaign authority.\n\nUse `$gitcrawl` for available archive discovery, `$openclaw-testing` for proof,\n`$autoreview` for independent code review, and `$crabbox` when the proof requires\nremote environment or untrusted-source isolation. Author-history research is\nconditional on a concrete question, not a campaign prerequisite.\n\n## Coordinate ownership\n\nAssign each item or shared root-cause cluster one owner, a checkout, frozen\nsource SHA, authorized actions, and a useful stopping condition. Duplicate\nsymptoms share an owner; repeated defect classes should be repaired in the\ncanonical owner rather than by parallel near-identical patches.\n\nUse isolated issue\u002FPR worktrees and preserve unrelated files. Serialize shared\nfetch\u002Fref\u002Fbranch\u002Fworktree operations, PR preparation, and merges in short slots;\nnever hold the slot across coding, tests, or a remote wait. Each remote lease has\none owner and one active command. Pause only campaign-owned work under resource\npressure, and preserve patches, claims, proof, and checkpoints before replacement.\nThe lead may take over stalled work safely; it is not an orchestration-only role.\n\nRead root and scoped guides before acting. Each verdict-bearing worker inspects\nits relevant dependency contracts directly, including the root's personal Codex\nsource requirement. The lead verifies consequential results, not just summaries.\nUse independent challenge for nontrivial repairs and closure evidence; one\nindependent autoreview is enough for the code-review requirement.\n\n## Investigate and repair\n\nSearch existing work before creating another fix: current body\u002Fcomments, related\narchive results, live state when it matters, and current source\u002Fhistory. Use bare\nPATH `gh` with narrow JSON fields; reuse shared evidence and avoid unnecessary\npagination or repeated item fetches.\n\nPrefer, in order:\n\n1. Prove the original behavior is already fixed on current main and close under\n   the authorized scope with the canonical fix and evidence.\n2. Finish and verify an existing useful editable PR, preserving human credit.\n3. If that PR cannot safely be updated, create a credited replacement before\n   closing it. Do not squash a contributor PR after replacing its ancestry.\n4. Implement a new high-confidence repair when no suitable fix exists.\n5. Record a concrete blocker or product\u002Fowner decision. A useful independent\n   simplification may land under its own scope, but it does not close the bug.\n\nA candidate needs a demonstrated current defect, an understood owner and\nbounded impact, relevant dependency proof, and feasible validation. Repairs\nrequiring new dependencies\u002Fconfiguration, public-contract changes, security,\npersistence design, or product judgment require their root approvals before\nimplementation or landing as applicable. Preserve useful investigation; do not\nwork around the gate or count review-required work as an accepted fix.\n\nRepair the invariant at its owner, cover relevant siblings, and remove connected\nobsolete paths when justified. Do not add speculative fallback layers or hardcode\nthe reported example. Prefer simplicity without a LOC quota. Keep release-note\ncontext and credit in the PR; `CHANGELOG.md` remains release-owned. Do not force a\nsecond refactor PR after each completed item.\n\n## Proof and landing\n\nChoose proportional proof through `$openclaw-testing`. Trusted development can\nrun locally; remote compute needs an environment or isolation reason. Untrusted\nrepository tooling never runs locally or on a credential-hydrated host. Preserve\nexplicit live requirements and never describe a mock, skipped test, old head, or\nunfinished soak as live proof.\n\nRun `$autoreview` on the completed nontrivial candidate and resolve verified\nfindings. Re-review substantive changes or unresolved concerns; do not multiply\nreviews for mechanical head movement. Address actionable human\u002Fbot findings\nwithout a separate Rank-up checklist or score-refresh gate.\n\nLand through the native maintainer workflow only with current required CI and\nreview evidence. Verify remote merge state and ancestry before counting success.\nA timed-out merge request may have succeeded; reconcile it before retrying.\nRefresh\u002Frebase for conflicts, failed guards, explicit requests, or material stale\nbase risk, not merely because main advanced. Delete only owned temporary state.\n\nFor broad campaigns, a shared-main failure may justify one separately scoped\nrepair worker. Check for an existing fix first. Do not duplicate that repair in\nevery PR or silently expand a bounded ref request to unrelated CI work.\n\n## Closure and reporting\n\nBefore closing, prove the reporter's primary outcome and affected surfaces are\nfixed, not merely mitigated or diagnosed. Check fix ancestry and containing tags\nwhen version claims matter; dates do not prove inclusion. Seek independent\nchallenge for uncertain or consequential closure evidence. Disagreement, a still\nbroken surface, or an owner hold means leave open. Product rejection is a\nmaintainer decision, never an automatic cleanup conclusion.\n\nRecheck live state before mutation and explain the fixed behavior, canonical\ncommit\u002FPR, known containing version, and useful proof. If a closure is challenged,\npause the affected closure work and correct the evidence before resuming. No more\nthan three workers should hold simultaneous closure duty; more than fifty\nclose\u002Freopen actions require the root's explicit count\u002Fscope approval.\n\nKeep a resumable ledger of owner, source\u002Fhead, outcome, proof\u002FCI state, PR\u002Fmerge,\ncredit, blockers, and cleanup. Count verified outcomes, not planned or launched\nwork. Report meaningful progress and each verified landing with links; summarize\nfinal behavior, proof, remaining limitations, and checkout state in natural prose.\n",{"name":5,"description":7},"main","f1c93577085244aa96aa87b53a2df9b59d293bd7",".agents\u002Fskills\u002Fopenclaw-repair-sweep",82862,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw","https:\u002F\u002Fopenclaw.ai","https:\u002F\u002Fgithub.com\u002Fopenclaw","Your personal, open source AI assistant.","2026-11-11 08:46:30",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add openclaw\u002Fopenclaw --skill openclaw-repair-sweep",{"tool":56,"command":57},"bunx","bunx skills add openclaw\u002Fopenclaw --skill openclaw-repair-sweep",{"tool":59,"command":60},"pnpm","pnpm dlx skills add openclaw\u002Fopenclaw --skill openclaw-repair-sweep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-repair-sweep\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"agents\u002Fopenai.yaml","REFERENCE","参考文档",362,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-repair-sweep\u002Fagents\u002Fopenai.yaml",[71,77,100,118,140,164],{"skillNo":72,"name":73,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":36},"01M698VP84FNM6G9MR1HPX7MF7","lobster","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Flobster\u002FSKILL.md",[],[73],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":36},"01M698YY8QGQ7S8TJNKJG6VTPH","xurl","xurl CLI for authenticated X posts, replies, reads\u002Fsearch, DMs, media upload, followers, auth status, or raw v2 API calls.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fxurl\u002FSKILL.md",[],[79,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99],"for","api","calls","replies","posts","upload","tap","install","brew","node","Media","search","npm","status","auth","cli",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":36},"01M698YWT1CJ0WK88WB909R9RT","weather","Current weather and forecasts with web_fetch, falling back to wttr.in curl for locations, rain, temperature, travel planning.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fweather\u002FSKILL.md",[],[102,107,108,91,109,92,110,111,112,113,114,115,84,116,117],"travel planning","travel","fetch","curl","https","help","planning","web","back","temperature","with",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":129,"publishedAt":36},"01M698YV2Q0R0JJKAWGFS21K0N","visualize","Create inline visuals for code and explanations, or author persistent OpenClaw dashboard widgets with show_widget.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fvisualize\u002FSKILL.md",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[120,130,131,132,133,84,117,134,135,136,137,138,9,139],"widgets","openclaw dashboard","author","inline","show","code","create","visuals","dashboard","widget",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":154,"publishedAt":36},"01M698YS2TRJH9ENG28HD9CD87","trello","Manage Trello boards, lists, and cards via the Trello REST API.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Ftrello\u002FSKILL.md",[146,151],{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":152,"categoryName":153,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000030","开发工程师",[142,111,155,156,157,158,159,160,91,92,161,110,85,162,163],"cloud","manage","via","rest api","token","atlassian","jq","REST","developer",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":36},"01M698YQ9Q3M4W78EWV2KSCSVW","tmux","Control tmux sessions\u002Fpanes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Ftmux\u002FSKILL.md",[],[166,91,171,172,84,173,174,175,176,177,178,179,92,180,181,182,183,184,185],"send","darwin","keys","paste","output","control","prompts","interactive","list","capture","panes","text","monitor","sessions","linux"]