[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E845T1XT4KE74S2FS7DRY9":3,"skill-same:01M7E845T1XT4KE74S2FS7DRY9":85},{"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":36,"commitSha":37,"skillDirectory":38,"forksCount":14,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":56},"01M7E845T1XT4KE74S2FS7DRY9","terraform-bump-terraform",null,"Use when updating the Terraform or OpenTofu CLI across module constraints, version-manager files, CI, and images.","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\u002Fterraform-bump-terraform\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: terraform-bump-terraform\ndescription: >-\n  Use when updating the Terraform or OpenTofu CLI across module constraints,\n  version-manager files, CI, and images.\ndisable-model-invocation: true\nallowed-tools: [\"Bash\", \"Read\", \"Grep\", \"Glob\", \"Edit\", \"Write\", \"AskUserQuestion\"]\nmetadata:\n  argument-hint: \"[version] [--root-module \u003Cdir>...] [--audit-only] [--no-lock] [--no-commit]\"\n  source: \"plugins\u002Fterraform\u002Fskills\u002Fbump-terraform\u002FSKILL.md\"\n---\n\n# Bump the Terraform CLI\n\nMove `required_version` across every module that declares one, along\nwith the version manager files, CI workflows, and images that pin the\nsame CLI somewhere else.\n\nFollow the conventions in the `terraform-bumping-terraform` skill (recorded tree\nstate, script paths, commit message rules, non-interactive defaults,\nthe plan, stopped and audit-only runs). This skill uses\n`references\u002Flayout-discovery.md`,\n`references\u002Fpin-sites.md`, and\n`references\u002Flock-and-init.md`. To move a provider, use\nthe `terraform-bump-provider` skill.\n\nUser arguments: $ARGUMENTS\n\n## Procedure\n\n### 1. Resolve the target version\n\nFind the installed CLI version with `terraform -version` or\n`tofu -version`, whichever exists. If the user named a version, confirm\nit with the by-key command in `references\u002Fpin-sites.md`. Otherwise list the latest stable releases:\n\n```console\n$ curl -fsS https:\u002F\u002Freleases.hashicorp.com\u002Fterraform\u002Findex.json \\\n    | jq -r '.versions | keys_unsorted[]' \\\n    | python3 references\u002Flockctl.py stable 3\n```\n\nWrite the script's absolute path there, per the umbrella's script-path rule.\n\nWhen `tofu` drives the repository, list OpenTofu's releases with the\ncommand in `references\u002Fpin-sites.md`. Present the latest stable\nalongside the installed version and confirm which to write; they often\ndiffer. If the release list is unreachable and the user named no\nversion, stop and ask which version to write. When the target crosses a\nmajor version, add the CLI's upgrade guide to the report.\n\n### 2. Discover the layout\n\nFollow `references\u002Flayout-discovery.md` and record its inventory.\n`--root-module` limits the run to the named directories.\n\n### 3. Inventory every pin site\n\nBoth kinds, per the pin-sites reference: `required_version` in every\nmodule (the reference searches `.tf`, `.tofu`, `.tf.json`, and `.tofu.json`\nbefore applying the selected tool's file precedence), and the pins outside the configuration (`.terraform-version`,\n`.tool-versions`, `mise.toml`, `.mise\u002Fconfig.toml`, workflow files, image tags, devcontainer\nconfiguration, Makefile variables, `atlantis.yaml`, `.pre-commit-config.yaml`).\nWith `--root-module`, apply the umbrella's scope rule to roots outside it\nthat call a child module whose `required_version` you would edit.\n\n### 4. Report the drift before overwriting it\n\nRoot modules that disagree about the CLI, a version manager file that\ncontradicts the configuration, CI installing a third version: surface\nall of it as a finding first. An exact `required_version` is a hard gate\n(see the pin-sites reference), so root modules that disagree cannot all\nbe run from one machine.\n\nWhen they disagree, ask: converge every root module on the target, or\nmove only the selected ones and report the rest as outstanding drift.\n\n### 5. Distinguish root modules from reusable ones\n\nRoot modules keep their existing shape: an exact pin stays exact, a\npessimistic constraint stays pessimistic. Reusable modules keep floors,\nper the pin-sites reference; say why in the commit body when you move\none.\n\n### 6. Present the plan and wait\n\nPer the umbrella's Orchestration Plan, show every site to be edited with the form it keeps, every site left\nalone with the reason, the drift found, and whether lock files will be\nrefreshed. Warn when the installed CLI cannot satisfy the new\n`required_version`: `init` will not run and the roots will be unverifiable. With `--audit-only`, stop here and write nothing.\n\n### 7. Edit and re-initialise\n\nEdit all pin sites, committing nothing yet. Unless `--no-lock`, check\nthat the installed CLI satisfies the new `required_version`; if it does\nnot, skip `init`, report it unverifiable, and name the installed version.\n\nOtherwise re-run `init` in each root module that has a committed,\nunmodified lock:\n\n- Use plain `init` per the lock reference, never `-upgrade`: a CLI bump\n  moves no provider. Compare with `lockctl.py diff` without `--allow`.\n  An unqualified pass requires exit 0.\n- A non-zero exit (any provider-block change, including checksums) means\n  restore the lock from git and report it.\n- A CLI bump can change the lock file's header outside provider blocks;\n  provider blocks must remain byte-identical unless the user explicitly\n  approves checksum loss under the lock reference's exception.\n- A root module with no committed lock is skipped and reported: `init`\n  there would create a lock and pick providers. Run it only after the\n  user approves that outcome.\n\nA failed `init`, or a lock restored for a provider-block change, stops\nthe run with nothing committed. Leave the pin edits in the\nworking tree and end with the stopped line (the umbrella has its mid-run\nform). The checksum-loss exception never permits a provider version or\nconstraint to change, and its report must state the approved reduction.\n\n### 8. Verify, then commit\n\nVerify on the working tree before any commit. Confirm each guarded root\nmodule initialised under the new version in the step above. Where `init`\ndid not run (`--no-lock`, a CLI that does not satisfy the pin, or no\ncommitted lock), report it unverifiable and edit nothing to work around\nit. Then run the repository's own gates (`validate`, `tflint`, policy\nchecks).\n\nApply [Verification gates](references\u002Flock-and-init.md#verification-gates)\nto classify failures before publication. When it requires a stop, leave the\nedits, commit nothing, and end with the stopped line.\n\nWith `--no-commit`, leave the edits in the working tree. Otherwise make\none commit holding the pin edits and any changed lock. Write commit\nmessages and the report per `references\u002Fprose-rules.md`.\n\n## Output\n\nOpen with a one-line hero (`✓ terraform \u003Cold> -> \u003Cnew> across N pin\nsites` or `Audit only: N sites disagree`; `\u003Cold>` is the version only when\nevery pin is exact and equal; otherwise `mixed`, never a range or a\n`1.9.x` shorthand). A floor or pessimistic constraint makes `\u003Cold>`\n`mixed` even when a version-manager file names an exact version. Then these sections in\norder:\n\n1. `## Target`: the resolved version, how it was confirmed (registry\n   or `\u003Cversion>, confirmed by you`), and the version installed locally.\n   Add a changelog link only after fetching it.\n2. `## Layout`: the discovered root modules and child modules (the umbrella\n   says when to name the tool).\n3. `## Sites`: every existing pin, inside the configuration and outside\n   it, and whether each was edited or left alone with the reason. A file\n   with no CLI pin is not a pin site; actionable missing pins go in `## Drift`.\n4. `## Locks`: per root module: whether the lock was re-initialised or\n   skipped (and why), and the `h1:` checksum counts before and after.\n   Report platform coverage unverified unless a successful command\n   checked the required platform names; counts alone do not prove it.\n5. `## Verification`: the gates run and their real results.\n6. `## Drift`: actionable missing pins or disagreements not already\n   reported in `## Sites`. Omit it when none remain. This section owns a\n   CI workflow's missing pin; do not repeat it in `## Sites`. An\n   installed-CLI mismatch belongs in `## Locks`, and a pre-existing gate failure\n   belongs in `## Verification`.\n\nName the commit by subject in `## Sites`, never by SHA.\nState a root module that could not be initialised in `## Locks` only;\n`## Verification` does not repeat it.\n\nReply in this shape, as plain text outside any code fence, with plain bullets, no bold (never `- **Label:** ...`), and no local paths:\n\n```text\n✓ terraform mixed -> 1.14.0 across 2 pin sites\n\n## Target\n\n- 1.14.0, confirmed by you; 1.16.5 installed locally.\n\n## Layout\n\n- Root module: infra\u002Fprod.\n\n## Sites\n\n- infra\u002Fprod\u002Fversions.tf: required_version ~> 1.9.0 to ~> 1.14.0.\n- .tool-versions: terraform 1.9.5 to 1.14.0.\n- Commit: \"Bump Terraform CLI to 1.14.0\".\n\n## Locks\n\n- infra\u002Fprod: initialization skipped because installed Terraform 1.16.5 does not satisfy ~> 1.14.0; initialization and validation unverified. The lock retains random 3.6.0 with 2 h1 records before and after; platform coverage unverified.\n\n## Verification\n\n- fmt -check passes.\n```\n\nA run that cannot proceed ends with the stopped line from\nthe `terraform-bumping-terraform` skill, not this shape, and has no\npanel and no `Next steps:` list.\n\nEnd with an `ask-user-choice` panel offering next steps, for example:\nconverge the root modules still on an older pin, add the version to a\nversion manager file the repository lacks, align the CI workflow, or\nstop here. Skip the panel only in plan mode. Without a question tool, print the\numbrella's `Next steps:` list and stop.\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","# Bump the Terraform CLI\n\nMove `required_version` across every module that declares one, along\nwith the version manager files, CI workflows, and images that pin the\nsame CLI somewhere else.\n\nFollow the conventions in the `terraform-bumping-terraform` skill (recorded tree\nstate, script paths, commit message rules, non-interactive defaults,\nthe plan, stopped and audit-only runs). This skill uses\n`references\u002Flayout-discovery.md`,\n`references\u002Fpin-sites.md`, and\n`references\u002Flock-and-init.md`. To move a provider, use\nthe `terraform-bump-provider` skill.\n\nUser arguments: $ARGUMENTS\n\n## Procedure\n\n### 1. Resolve the target version\n\nFind the installed CLI version with `terraform -version` or\n`tofu -version`, whichever exists. If the user named a version, confirm\nit with the by-key command in `references\u002Fpin-sites.md`. Otherwise list the latest stable releases:\n\n```console\n$ curl -fsS https:\u002F\u002Freleases.hashicorp.com\u002Fterraform\u002Findex.json \\\n    | jq -r '.versions | keys_unsorted[]' \\\n    | python3 references\u002Flockctl.py stable 3\n```\n\nWrite the script's absolute path there, per the umbrella's script-path rule.\n\nWhen `tofu` drives the repository, list OpenTofu's releases with the\ncommand in `references\u002Fpin-sites.md`. Present the latest stable\nalongside the installed version and confirm which to write; they often\ndiffer. If the release list is unreachable and the user named no\nversion, stop and ask which version to write. When the target crosses a\nmajor version, add the CLI's upgrade guide to the report.\n\n### 2. Discover the layout\n\nFollow `references\u002Flayout-discovery.md` and record its inventory.\n`--root-module` limits the run to the named directories.\n\n### 3. Inventory every pin site\n\nBoth kinds, per the pin-sites reference: `required_version` in every\nmodule (the reference searches `.tf`, `.tofu`, `.tf.json`, and `.tofu.json`\nbefore applying the selected tool's file precedence), and the pins outside the configuration (`.terraform-version`,\n`.tool-versions`, `mise.toml`, `.mise\u002Fconfig.toml`, workflow files, image tags, devcontainer\nconfiguration, Makefile variables, `atlantis.yaml`, `.pre-commit-config.yaml`).\nWith `--root-module`, apply the umbrella's scope rule to roots outside it\nthat call a child module whose `required_version` you would edit.\n\n### 4. Report the drift before overwriting it\n\nRoot modules that disagree about the CLI, a version manager file that\ncontradicts the configuration, CI installing a third version: surface\nall of it as a finding first. An exact `required_version` is a hard gate\n(see the pin-sites reference), so root modules that disagree cannot all\nbe run from one machine.\n\nWhen they disagree, ask: converge every root module on the target, or\nmove only the selected ones and report the rest as outstanding drift.\n\n### 5. Distinguish root modules from reusable ones\n\nRoot modules keep their existing shape: an exact pin stays exact, a\npessimistic constraint stays pessimistic. Reusable modules keep floors,\nper the pin-sites reference; say why in the commit body when you move\none.\n\n### 6. Present the plan and wait\n\nPer the umbrella's Orchestration Plan, show every site to be edited with the form it keeps, every site left\nalone with the reason, the drift found, and whether lock files will be\nrefreshed. Warn when the installed CLI cannot satisfy the new\n`required_version`: `init` will not run and the roots will be unverifiable. With `--audit-only`, stop here and write nothing.\n\n### 7. Edit and re-initialise\n\nEdit all pin sites, committing nothing yet. Unless `--no-lock`, check\nthat the installed CLI satisfies the new `required_version`; if it does\nnot, skip `init`, report it unverifiable, and name the installed version.\n\nOtherwise re-run `init` in each root module that has a committed,\nunmodified lock:\n\n- Use plain `init` per the lock reference, never `-upgrade`: a CLI bump\n  moves no provider. Compare with `lockctl.py diff` without `--allow`.\n  An unqualified pass requires exit 0.\n- A non-zero exit (any provider-block change, including checksums) means\n  restore the lock from git and report it.\n- A CLI bump can change the lock file's header outside provider blocks;\n  provider blocks must remain byte-identical unless the user explicitly\n  approves checksum loss under the lock reference's exception.\n- A root module with no committed lock is skipped and reported: `init`\n  there would create a lock and pick providers. Run it only after the\n  user approves that outcome.\n\nA failed `init`, or a lock restored for a provider-block change, stops\nthe run with nothing committed. Leave the pin edits in the\nworking tree and end with the stopped line (the umbrella has its mid-run\nform). The checksum-loss exception never permits a provider version or\nconstraint to change, and its report must state the approved reduction.\n\n### 8. Verify, then commit\n\nVerify on the working tree before any commit. Confirm each guarded root\nmodule initialised under the new version in the step above. Where `init`\ndid not run (`--no-lock`, a CLI that does not satisfy the pin, or no\ncommitted lock), report it unverifiable and edit nothing to work around\nit. Then run the repository's own gates (`validate`, `tflint`, policy\nchecks).\n\nApply [Verification gates](references\u002Flock-and-init.md#verification-gates)\nto classify failures before publication. When it requires a stop, leave the\nedits, commit nothing, and end with the stopped line.\n\nWith `--no-commit`, leave the edits in the working tree. Otherwise make\none commit holding the pin edits and any changed lock. Write commit\nmessages and the report per `references\u002Fprose-rules.md`.\n\n## Output\n\nOpen with a one-line hero (`✓ terraform \u003Cold> -> \u003Cnew> across N pin\nsites` or `Audit only: N sites disagree`; `\u003Cold>` is the version only when\nevery pin is exact and equal; otherwise `mixed`, never a range or a\n`1.9.x` shorthand). A floor or pessimistic constraint makes `\u003Cold>`\n`mixed` even when a version-manager file names an exact version. Then these sections in\norder:\n\n1. `## Target`: the resolved version, how it was confirmed (registry\n   or `\u003Cversion>, confirmed by you`), and the version installed locally.\n   Add a changelog link only after fetching it.\n2. `## Layout`: the discovered root modules and child modules (the umbrella\n   says when to name the tool).\n3. `## Sites`: every existing pin, inside the configuration and outside\n   it, and whether each was edited or left alone with the reason. A file\n   with no CLI pin is not a pin site; actionable missing pins go in `## Drift`.\n4. `## Locks`: per root module: whether the lock was re-initialised or\n   skipped (and why), and the `h1:` checksum counts before and after.\n   Report platform coverage unverified unless a successful command\n   checked the required platform names; counts alone do not prove it.\n5. `## Verification`: the gates run and their real results.\n6. `## Drift`: actionable missing pins or disagreements not already\n   reported in `## Sites`. Omit it when none remain. This section owns a\n   CI workflow's missing pin; do not repeat it in `## Sites`. An\n   installed-CLI mismatch belongs in `## Locks`, and a pre-existing gate failure\n   belongs in `## Verification`.\n\nName the commit by subject in `## Sites`, never by SHA.\nState a root module that could not be initialised in `## Locks` only;\n`## Verification` does not repeat it.\n\nReply in this shape, as plain text outside any code fence, with plain bullets, no bold (never `- **Label:** ...`), and no local paths:\n\n```text\n✓ terraform mixed -> 1.14.0 across 2 pin sites\n\n## Target\n\n- 1.14.0, confirmed by you; 1.16.5 installed locally.\n\n## Layout\n\n- Root module: infra\u002Fprod.\n\n## Sites\n\n- infra\u002Fprod\u002Fversions.tf: required_version ~> 1.9.0 to ~> 1.14.0.\n- .tool-versions: terraform 1.9.5 to 1.14.0.\n- Commit: \"Bump Terraform CLI to 1.14.0\".\n\n## Locks\n\n- infra\u002Fprod: initialization skipped because installed Terraform 1.16.5 does not satisfy ~> 1.14.0; initialization and validation unverified. The lock retains random 3.6.0 with 2 h1 records before and after; platform coverage unverified.\n\n## Verification\n\n- fmt -check passes.\n```\n\nA run that cannot proceed ends with the stopped line from\nthe `terraform-bumping-terraform` skill, not this shape, and has no\npanel and no `Next steps:` list.\n\nEnd with an `ask-user-choice` panel offering next steps, for example:\nconverge the root modules still on an older pin, add the version to a\nversion manager file the repository lacks, align the CI workflow, or\nstop here. Skip the panel only in plan mode. Without a question tool, print the\numbrella's `Next steps:` list and stop.\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,"disable-model-invocation":35},{"source":25,"argument-hint":26},"plugins\u002Fterraform\u002Fskills\u002Fbump-terraform\u002FSKILL.md","[version] [--root-module \u003Cdir>...] [--audit-only] [--no-lock] [--no-commit]",[28,29,30,31,32,33,34],"Bash","Read","Grep","Glob","Edit","Write","AskUserQuestion",true,"main","5fbeb3b47beedea13813be7b7023f736a8d97a65",".agents\u002Fskills\u002Fterraform-bump-terraform","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":45,"prompt":55,"zipAvailable":35},[46,49,52],{"tool":47,"command":48},"npx","npx skills add tony\u002Fskills --skill terraform-bump-terraform",{"tool":50,"command":51},"bunx","bunx skills add tony\u002Fskills --skill terraform-bump-terraform",{"tool":53,"command":54},"pnpm","pnpm dlx skills add tony\u002Fskills --skill terraform-bump-terraform","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fterraform-bump-terraform\u002FSKILL.md",[57,63,67,71,77,81],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"agents\u002Fopenai.yaml","REFERENCE","参考文档",304,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fterraform-bump-terraform\u002Fagents\u002Fopenai.yaml",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Flayout-discovery.md",7410,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fterraform-bump-terraform\u002Freferences\u002Flayout-discovery.md",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Flock-and-init.md",14822,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fterraform-bump-terraform\u002Freferences\u002Flock-and-init.md",{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Flockctl.py","SCRIPT","脚本",10050,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fterraform-bump-terraform\u002Freferences\u002Flockctl.py",{"path":78,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fpin-sites.md",11775,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fterraform-bump-terraform\u002Freferences\u002Fpin-sites.md",{"path":82,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fprose-rules.md",4644,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fterraform-bump-terraform\u002Freferences\u002Fprose-rules.md",[86,93,100,107,114,121],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"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",[],[]]