Add publish-vscode-extension skill#4
Open
spoenemann wants to merge 1 commit into
Open
Conversation
Covers preparing and publishing a VS Code extension to both the VS Code Marketplace and the Open VSX Registry, with reference files for the package.json manifest, bundling with esbuild/webpack, and each registry's authentication and publisher/namespace model. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
New skill that helps prepare and publish a VS Code extension to the VS Code Marketplace, the Open VSX Registry, or both. SKILL.md carries the shared workflow (package once with vsce, publish the same .vsix to each registry, safe token handling); the four references cover the package.json manifest, bundling with esbuild/webpack, the Azure DevOps/vsce side, and the Eclipse/ovsx side including namespace ownership.
Motivation
Publishing across both registries spans two identity systems, two auth flows, and several non-obvious gotchas — PAT scopes, namespace ownership and the "unverified" warning, Web Extension bundling requirements, etc. Capturing it as a skill avoids re-deriving the workflow each time and makes the token-handling rules explicit so the agent never asks the user to paste a token into the conversation.