Skillshub vscode-ext-commands
Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices
install
source · Clone the upstream repo
git clone https://github.com/ComeOnOliver/skillshub
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ComeOnOliver/skillshub "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/github/awesome-copilot/vscode-ext-commands" ~/.claude/skills/comeonoliver-skillshub-vscode-ext-commands && rm -rf "$T"
manifest:
skills/github/awesome-copilot/vscode-ext-commands/SKILL.mdsource content
VS Code extension command contribution
This skill helps you to contribute commands in VS Code extensions
When to use this skill
Use this skill when you need to:
- Add or update commands to your VS Code extension
Instructions
VS Code commands must always define a
title, independent of its category, visibility or location. We use a few patterns for each "kind" of command, with some characteristics, described below:
-
Regular commands: By default, all commands should be accessible in the Command Palette, must define a
, and don't need ancategory
, unless the command will be used in the Side Bar.icon -
Side Bar commands: Its name follows a special pattern, starting with underscore (
) and suffixed with_
, like#sideBar
for instance. Must define an_extensionId.someCommand#sideBar
, and may or may not have some rule foricon
. Side Bar exclusive commands should not be visible in the Command Palette. Contributing it to theenablement
orview/title
, we must inform order/position that it will be displayed, and we can use terms "relative to other command/button" in order to you identify the correctview/item/context
to be used. Also, it's a good practice to define the condition (group
) for the new command is visible.when