菜单
Use when: versioning the bundled controller extension VSIX, bumping packages/controller-extension/package.json, updating extension version history/changelog, auto-incrementing semver, preparing controller VSIX releases.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | extension-versioning |
| description | Use when: versioning the bundled controller extension VSIX, bumping packages/controller-extension/package.json, updating extension version history/changelog, auto-incrementing semver, preparing controller VSIX releases. |
Use this skill whenever a task asks to version, bump, release, package, or track the bundled controller extension VSIX in this repository.
The controller extension version is independent from the CLI package version. Do not force root, CLI, and controller package versions to match.
packages/controller-extension/package.jsonpackage-lock.jsonextension-version-history.jsonCHANGELOG.mdThe version represents the bundled controller extension VSIX installed by
vscode-ext-test install-into-profile and vscode-ext-test update.
Whenever a functional change touches packages/controller-extension/**, bump
the controller extension version before final packaging. CLI-only changes do not
require a controller extension bump.
patch for controller extension fixes or hardeningminor for new controller extension capabilities or protocol additionsmajor for breaking controller extension protocol or activation changesx.y.z only when the user asks for a specific versionnpm run version:extension -- patch --dry-run --note "short release note"
npm run version:extension -- patch --note "short release note"
package.json and
packages/cli/package.json.packages/cli/package.json; the release workflow
enforces that separately and does not require the controller VSIX version to match.E2E test and verify VS Code extension behavior using vscode-extension-tester. Write Gherkin .feature files, run them against an isolated VS Code instance with full capabilities (CDP, input automation, DOM interaction), and review structured test results and artifacts.
Use when: finalizing a fix or feature in vscode-extension-tester, rebuilding CLI dist, rebuilding the bundled controller VSIX, packaging release artifacts, and verifying vscode-ext-test install-into-project/update deploy the latest assets to other projects.
Use when: shipping binary releases through the existing GitHub Actions release workflow, creating or pushing vX.Y.Z git tags, verifying release tag/package version alignment, publishing release artifacts.