[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E7SDKVR4N6Q8AE339E2DPJ":3,"skill-same:01M7E7SDKVR4N6Q8AE339E2DPJ":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":14,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M7E7SDKVR4N6Q8AE339E2DPJ","merge-pr-merge-many",null,"Use when a user explicitly wants to land several PRs, or all of them, in turn: stacked or independent, rebased, CI-watched, each merged via gh.","tony\u002Fskills","tony","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F26336?v=4","01M72E5RNJ7SQV8F9KBM5RKRMN","Tony Narlock","01M7E7MBN5C6YZ4JJJ5Y82KBJG",0,"MIT","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmerge-pr-merge-many\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: merge-pr-merge-many\ndescription: >-\n  Use when a user explicitly wants to land several PRs, or all of them, in\n  turn: stacked or independent, rebased, CI-watched, each merged via gh.\nallowed-tools: [\"Bash\", \"Read\", \"Write\", \"Edit\", \"AskUserQuestion\"]\nmetadata:\n  argument-hint: \"[PR numbers\u002FURLs, e.g. '#31 #32'] [--squash | --rebase | any other gh pr merge flag]\"\n  source: \"plugins\u002Fmerge-pr\u002Fskills\u002Fmerge-many\u002FSKILL.md\"\n---\n\n# Merge Multiple PRs\n\nLand a set of pull requests one at a time: merge one, refresh trunk,\nbring the next PR up to date (rebase, resolve conflicts, force-push,\nwait on CI), then merge it, repeating until the set is landed or a\ngate halts the run.\n\nRead `references\u002Fmerge-readiness.md` before touching any PR.\n\nUser arguments: $ARGUMENTS\n\n## Procedure\n\n### 1. Assemble the roster\n\nTake the PR set from the arguments, or from the PRs this\nconversation has been working on. If the set is ambiguous (the\nconversation touched more PRs than the user likely means, or an\nargument doesn't match an open PR), present the candidates via\n`ask-user-choice` and let the user pick; without a question tool, halt and\nlist them. Show the final roster.\n\nRead each roster PR's `mergeStateStatus` (`gh pr view \u003Cn> --json mergeStateStatus`).\nWhen any is `BEHIND` or `DIRTY`, confirm via `ask-user-choice` before the\nfirst merge, naming each such PR and its branch as a force-push\n(`--force-with-lease --force-if-includes`). The approval also covers a\nroster PR that falls behind after an earlier merge. Without a question tool,\nor if the user declines, halt before any rebase or push. When every PR is\n`CLEAN`, the approval is still asked at the first PR that needs a rebase.\n\nList the open PRs to check the roster against. A failure means `gh` is\nunavailable or unauthenticated: report it and stop. `--limit` lifts the\ndefault cap of 30; a roster PR missing from the list is checked with\n`gh pr view \u003Cn>` before it is called not open.\n\n```console\n$ gh pr list --limit 200 --json number,title,headRefName,baseRefName,isDraft\n```\n\n### 2. Detect the topology\n\nCheck the repo scope as the reference describes. Then have the helper read\neach PR and order the set, passing `--repo` when the user did:\n\n```console\n$ python3 \u002Fabsolute\u002Fpath\u002Fto\u002Fscripts\u002Fmerge_pr.py order \u003CPR numbers in the user's order>\n```\n\nIt prints the topology (`stack` when any PR's base branch is another PR's\nhead branch, else `independent`), the merge order (bottom-up for a stack,\notherwise the order given), the trunk, each PR's parent, and each\n`headRefOid`; keep the `headRefOid` values for the stacked rebase. A `null`\ntrunk means the PRs target different branches: ask which is trunk, or halt\nand list them without a question tool.\n\nResolve the absolute script path as the reference describes: `..\u002F..\u002Fscripts\u002F`\nfrom this skill's directory.\n\nFor a stack, plan the retarget: after each parent merges, read the child's\n`baseRefName` (`gh pr view \u003Cchild> --json baseRefName`); when it is not\ntrunk, run `gh pr edit \u003Cchild> --base \u003Ctrunk>`, then re-read the child's\nstate, before its readiness gate.\n\n### 3. Land each PR\n\nOne PR at a time; never merge two PRs between trunk syncs. For each PR in\norder:\n\n1. **Retarget** a stacked child whose parent just merged, as planned above.\n2. **Readiness gate**: apply the gate from the reference, on the\n   retargeted state. A halt reports what landed and what remains.\n3. **Bring up to date**: when the PR is `BEHIND` or `DIRTY` (or `UNKNOWN`\n   after the gate's retries) and the force-push is approved, follow the\n   reference's rebase procedure; unapproved, ask as in step 1 or halt; with\n   scope `remote` that halts the run. Leave a `CLEAN` PR alone: no rebase,\n   no force-push. For a stacked child, use its `--onto` form with the\n   parent's roster-time `headRefOid`, because a squash merge leaves the\n   parent's old head out of trunk. Ask on any conflict that forces a choice\n   between behaviors.\n4. **Wait on CI**: `gh pr checks \u003Cn> --watch` only when the PR was rebased or\n   the gate saw pending checks. A PR with no checks has no CI to wait on.\n5. **Merge**: check the repo allows the strategy, compose the message per\n   the reference and `references\u002Fprose-rules.md` (no `Co-Authored-By`,\n   no \"Generated with\" or other tool trailer, no emoji), then merge with\n   the reference's `merge_pr.py merge` command, never a message inside a\n   shell string, with `--match-head-commit \u003Csha>` and the strategy flag. Pass the\n   user's other flags through verbatim, except `--delete-branch` on a stack\n   parent: the reference drops it, and the report says so.\n6. **Sync**: per the reference's \"After each merge\", including its check\n   that trunk contains the merge commit and the subject read-back. A queued\n   (`--auto`) merge halts the run here.\n\n### 4. Halt conditions\n\nStop and report, never push past, when a rebase produces an\nunexpected content diff, CI fails on a rebased head, a PR turned\nclosed or draft mid-run, or a conflict needs a product decision.\nEverything already merged stays merged; the report says exactly\nwhere the run stopped and why.\n\nAfter the last PR of a stack merges, carry out the user's `--delete-branch`\nfor every branch still on the remote, per the reference's stack-parents section.\n\n## Output\n\nOpen with a one-line hero (`✓ Merged N of M PRs`, or\n`⚠ Merged N of M PRs; \u003Ctrunk fact>` when a contains-the-merge-commit check\nfailed or a subject was not verified, or\n`⚠ Halted at #N: \u003Creason>`; an `--auto` merge halts with\n`⚠ Halted at #N: queued with --auto, merges once checks pass`), then\nexactly these sections. Report only what\na command in this run verified, and name the merge order only once the\ntopology was read. A run halted before any merge (`gh` unavailable, roster\ninvalid) gives the hero and one sentence on what the user must do; no\nheadings, and never a sentence saying what was not done (\"nothing was\nmerged\"). The hero states the cause only: not \"so neither PR was merged\".\n\n1. `## Roster`: the PRs, detected topology (stack or independent),\n   and merge order.\n2. `## Merges`: one bullet per PR: the gate result, rebase and conflicts if\n   any (a clean rebase is \"rebased onto \u003Cbase>; previous head \u003Cshort sha>\", nothing more), CI outcome, merge commit short SHA with its subject as read back from\n   the commit. Note a dropped `--delete-branch` on a stack parent, and the\n   parent branches deleted after the last merge. Diagnostics about the\n   environment belong in no bullet. Name a flag only when the run\n   dropped or added one; never the user's own flags.\n3. `## Trunk`: the post-run trunk state and the result of the\n   contains-the-merge-commit check. Report a mismatch as a fact with the\n   short SHAs; give no cause.\n\nState a failure as the fact the user needs; never quote the tool's error\ntext or explain how a check works. Follow the reference's \"Report wording\".\nWrite the sections per `references\u002Fprose-rules.md`, impersonally:\nno first person.\n\nReply in this shape, as plain text outside any code fence, with plain\nbullets, no bold (never `- **Label:** ...`), and no local paths:\n\n```text\n⚠ Halted at #32: CI failed on the rebased head.\n\n## Roster\n\n- Stack of 3 PRs, merged bottom-up: #31, #32, #33.\n\n## Merges\n\n- #31: gate passed, CI green, merged as 4f2a9c1 \"sync(fix[client]) Retry transient network errors (#31)\".\n- #32: rebased onto main (previous head 9ad03e1); the type-check job failed. Not merged.\n- #33: not attempted.\n\n## Trunk\n\n- main is at the #31 merge commit.\n```\n\nA run halted before any merge:\n\n```text\n⚠ Halted: gh is not authenticated.\n\nRun `gh auth login`, then re-run `merge-pr-merge-many #31 #32 --squash`.\n```\n\nEnd with an `ask-user-choice` panel offering next steps (for\nexample: continue with a halted PR after a fix, merge another set,\nstop here); skip the panel in plan mode. Without a question tool, end\nafter the sections and say nothing about the missing panel; no\n`## Next steps` section.\n\n\n## Portability notes\n\n- `ask-user-choice` — present the listed options and wait for the user to pick one. Hosts with a structured multiple-choice tool (Claude Code's `AskUserQuestion`) should use it; otherwise print a numbered list and wait for a numbered reply. Never proceed on an assumed answer.\n- `$ARGUMENTS` — the text the user passed when invoking this skill. If your host does not substitute it, read it as the user's request in the current turn, and ask when there is none.\n- Bundled files — every relative path in this skill points at a file shipped inside this skill directory. Read them from here, not from the host's plugin tree.\n","# Merge Multiple PRs\n\nLand a set of pull requests one at a time: merge one, refresh trunk,\nbring the next PR up to date (rebase, resolve conflicts, force-push,\nwait on CI), then merge it, repeating until the set is landed or a\ngate halts the run.\n\nRead `references\u002Fmerge-readiness.md` before touching any PR.\n\nUser arguments: $ARGUMENTS\n\n## Procedure\n\n### 1. Assemble the roster\n\nTake the PR set from the arguments, or from the PRs this\nconversation has been working on. If the set is ambiguous (the\nconversation touched more PRs than the user likely means, or an\nargument doesn't match an open PR), present the candidates via\n`ask-user-choice` and let the user pick; without a question tool, halt and\nlist them. Show the final roster.\n\nRead each roster PR's `mergeStateStatus` (`gh pr view \u003Cn> --json mergeStateStatus`).\nWhen any is `BEHIND` or `DIRTY`, confirm via `ask-user-choice` before the\nfirst merge, naming each such PR and its branch as a force-push\n(`--force-with-lease --force-if-includes`). The approval also covers a\nroster PR that falls behind after an earlier merge. Without a question tool,\nor if the user declines, halt before any rebase or push. When every PR is\n`CLEAN`, the approval is still asked at the first PR that needs a rebase.\n\nList the open PRs to check the roster against. A failure means `gh` is\nunavailable or unauthenticated: report it and stop. `--limit` lifts the\ndefault cap of 30; a roster PR missing from the list is checked with\n`gh pr view \u003Cn>` before it is called not open.\n\n```console\n$ gh pr list --limit 200 --json number,title,headRefName,baseRefName,isDraft\n```\n\n### 2. Detect the topology\n\nCheck the repo scope as the reference describes. Then have the helper read\neach PR and order the set, passing `--repo` when the user did:\n\n```console\n$ python3 \u002Fabsolute\u002Fpath\u002Fto\u002Fscripts\u002Fmerge_pr.py order \u003CPR numbers in the user's order>\n```\n\nIt prints the topology (`stack` when any PR's base branch is another PR's\nhead branch, else `independent`), the merge order (bottom-up for a stack,\notherwise the order given), the trunk, each PR's parent, and each\n`headRefOid`; keep the `headRefOid` values for the stacked rebase. A `null`\ntrunk means the PRs target different branches: ask which is trunk, or halt\nand list them without a question tool.\n\nResolve the absolute script path as the reference describes: `..\u002F..\u002Fscripts\u002F`\nfrom this skill's directory.\n\nFor a stack, plan the retarget: after each parent merges, read the child's\n`baseRefName` (`gh pr view \u003Cchild> --json baseRefName`); when it is not\ntrunk, run `gh pr edit \u003Cchild> --base \u003Ctrunk>`, then re-read the child's\nstate, before its readiness gate.\n\n### 3. Land each PR\n\nOne PR at a time; never merge two PRs between trunk syncs. For each PR in\norder:\n\n1. **Retarget** a stacked child whose parent just merged, as planned above.\n2. **Readiness gate**: apply the gate from the reference, on the\n   retargeted state. A halt reports what landed and what remains.\n3. **Bring up to date**: when the PR is `BEHIND` or `DIRTY` (or `UNKNOWN`\n   after the gate's retries) and the force-push is approved, follow the\n   reference's rebase procedure; unapproved, ask as in step 1 or halt; with\n   scope `remote` that halts the run. Leave a `CLEAN` PR alone: no rebase,\n   no force-push. For a stacked child, use its `--onto` form with the\n   parent's roster-time `headRefOid`, because a squash merge leaves the\n   parent's old head out of trunk. Ask on any conflict that forces a choice\n   between behaviors.\n4. **Wait on CI**: `gh pr checks \u003Cn> --watch` only when the PR was rebased or\n   the gate saw pending checks. A PR with no checks has no CI to wait on.\n5. **Merge**: check the repo allows the strategy, compose the message per\n   the reference and `references\u002Fprose-rules.md` (no `Co-Authored-By`,\n   no \"Generated with\" or other tool trailer, no emoji), then merge with\n   the reference's `merge_pr.py merge` command, never a message inside a\n   shell string, with `--match-head-commit \u003Csha>` and the strategy flag. Pass the\n   user's other flags through verbatim, except `--delete-branch` on a stack\n   parent: the reference drops it, and the report says so.\n6. **Sync**: per the reference's \"After each merge\", including its check\n   that trunk contains the merge commit and the subject read-back. A queued\n   (`--auto`) merge halts the run here.\n\n### 4. Halt conditions\n\nStop and report, never push past, when a rebase produces an\nunexpected content diff, CI fails on a rebased head, a PR turned\nclosed or draft mid-run, or a conflict needs a product decision.\nEverything already merged stays merged; the report says exactly\nwhere the run stopped and why.\n\nAfter the last PR of a stack merges, carry out the user's `--delete-branch`\nfor every branch still on the remote, per the reference's stack-parents section.\n\n## Output\n\nOpen with a one-line hero (`✓ Merged N of M PRs`, or\n`⚠ Merged N of M PRs; \u003Ctrunk fact>` when a contains-the-merge-commit check\nfailed or a subject was not verified, or\n`⚠ Halted at #N: \u003Creason>`; an `--auto` merge halts with\n`⚠ Halted at #N: queued with --auto, merges once checks pass`), then\nexactly these sections. Report only what\na command in this run verified, and name the merge order only once the\ntopology was read. A run halted before any merge (`gh` unavailable, roster\ninvalid) gives the hero and one sentence on what the user must do; no\nheadings, and never a sentence saying what was not done (\"nothing was\nmerged\"). The hero states the cause only: not \"so neither PR was merged\".\n\n1. `## Roster`: the PRs, detected topology (stack or independent),\n   and merge order.\n2. `## Merges`: one bullet per PR: the gate result, rebase and conflicts if\n   any (a clean rebase is \"rebased onto \u003Cbase>; previous head \u003Cshort sha>\", nothing more), CI outcome, merge commit short SHA with its subject as read back from\n   the commit. Note a dropped `--delete-branch` on a stack parent, and the\n   parent branches deleted after the last merge. Diagnostics about the\n   environment belong in no bullet. Name a flag only when the run\n   dropped or added one; never the user's own flags.\n3. `## Trunk`: the post-run trunk state and the result of the\n   contains-the-merge-commit check. Report a mismatch as a fact with the\n   short SHAs; give no cause.\n\nState a failure as the fact the user needs; never quote the tool's error\ntext or explain how a check works. Follow the reference's \"Report wording\".\nWrite the sections per `references\u002Fprose-rules.md`, impersonally:\nno first person.\n\nReply in this shape, as plain text outside any code fence, with plain\nbullets, no bold (never `- **Label:** ...`), and no local paths:\n\n```text\n⚠ Halted at #32: CI failed on the rebased head.\n\n## Roster\n\n- Stack of 3 PRs, merged bottom-up: #31, #32, #33.\n\n## Merges\n\n- #31: gate passed, CI green, merged as 4f2a9c1 \"sync(fix[client]) Retry transient network errors (#31)\".\n- #32: rebased onto main (previous head 9ad03e1); the type-check job failed. Not merged.\n- #33: not attempted.\n\n## Trunk\n\n- main is at the #31 merge commit.\n```\n\nA run halted before any merge:\n\n```text\n⚠ Halted: gh is not authenticated.\n\nRun `gh auth login`, then re-run `merge-pr-merge-many #31 #32 --squash`.\n```\n\nEnd with an `ask-user-choice` panel offering next steps (for\nexample: continue with a halted PR after a fix, merge another set,\nstop here); skip the panel in plan mode. Without a question tool, end\nafter the sections and say nothing about the missing panel; no\n`## Next steps` section.\n\n\n## Portability notes\n\n- `ask-user-choice` — present the listed options and wait for the user to pick one. Hosts with a structured multiple-choice tool (Claude Code's `AskUserQuestion`) should use it; otherwise print a numbered list and wait for a numbered reply. Never proceed on an assumed answer.\n- `$ARGUMENTS` — the text the user passed when invoking this skill. If your host does not substitute it, read it as the user's request in the current turn, and ask when there is none.\n- Bundled files — every relative path in this skill points at a file shipped inside this skill directory. Read them from here, not from the host's plugin tree.\n",{"name":5,"metadata":24,"description":7,"allowed-tools":27},{"source":25,"argument-hint":26},"plugins\u002Fmerge-pr\u002Fskills\u002Fmerge-many\u002FSKILL.md","[PR numbers\u002FURLs, e.g. '#31 #32'] [--squash | --rebase | any other gh pr merge flag]",[28,29,30,31,32],"Bash","Read","Write","Edit","AskUserQuestion","main","5fbeb3b47beedea13813be7b7023f736a8d97a65",".agents\u002Fskills\u002Fmerge-pr-merge-many","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills","https:\u002F\u002Fgithub.com\u002Ftony","https:\u002F\u002Ftony.sh","lighthouse keeper","2026-11-08 17:57:34",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add tony\u002Fskills --skill merge-pr-merge-many",{"tool":47,"command":48},"bunx","bunx skills add tony\u002Fskills --skill merge-pr-merge-many",{"tool":50,"command":51},"pnpm","pnpm dlx skills add tony\u002Fskills --skill merge-pr-merge-many","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmerge-pr-merge-many\u002FSKILL.md",true,[55,61,67,71],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"agents\u002Fopenai.yaml","REFERENCE","参考文档",255,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmerge-pr-merge-many\u002Fagents\u002Fopenai.yaml",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fmerge_pr.py","SCRIPT","脚本",12335,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmerge-pr-merge-many\u002Freferences\u002Fmerge_pr.py",{"path":68,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fmerge-readiness.md",16579,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmerge-pr-merge-many\u002Freferences\u002Fmerge-readiness.md",{"path":72,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fprose-rules.md",4644,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmerge-pr-merge-many\u002Freferences\u002Fprose-rules.md",[76,83,90,97,104,111],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7E8NCSHXV2JPW4J61R0TQS7","serene-bliss","Use when asked to make a CLI --help, docs page, error message, or tooling UX more serene or calmer for developer experience; returns text, no edits.","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Fserene-bliss\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7E8N87MAVJD8RRQKQB1ZPS6","review","Weave code review: run independent adversarial reviews in parallel, then synthesize findings","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7E8N402XG4ZBFNACQ413163","refine","Use when asked to refine a draft, iterate on code until cleaner, or polish a README through repeated critique and improvement.","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Frefine\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7E8N01KB86A7136P00GVKJW","prompt","Weave prompt: compare independent adversarial implementations, then adopt the single best one","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Fprompt\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7E8MW7YJW2PCMDW3G9RTGNK","plan","Weave planning: compare independent adversarial plans, then synthesize the best one","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Fplan\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M7E8MSBYXNCV4ZYWDS4PFJXK","fix-review","Fix weave review findings: validate, add test coverage, fix, and commit each as atomic changes","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Ffix-review\u002FSKILL.md",[],[]]