Coding & Refactoringlow risk
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
github/awesome-copilot·skills/vscode-ext-commands/SKILL.md
100/ 100Quality
Install this skill
Choose your coding agent and copy a project or personal installation command.
Project installation.agents/skills/vscode-ext-commands
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/vscode-ext-commands -a codex -yPersonal installation~/.agents/skills/vscode-ext-commands
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/vscode-ext-commands -a codex -g -yProject installation.claude/skills/vscode-ext-commands
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/vscode-ext-commands -a claude-code -yPersonal installation~/.claude/skills/vscode-ext-commands
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/vscode-ext-commands -a claude-code -g -yProject installation.agents/skills/vscode-ext-commands
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/vscode-ext-commands -a github-copilot -yPersonal installation~/.copilot/skills/vscode-ext-commands
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/vscode-ext-commands -a github-copilot -g -yProject installation.agents/skills/vscode-ext-commands
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/vscode-ext-commands -a cursor -yPersonal installation~/.cursor/skills/vscode-ext-commands
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/vscode-ext-commands -a cursor -g -yProject installation.agents/skills/vscode-ext-commands
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/vscode-ext-commands -a gemini-cli -yPersonal installation~/.gemini/skills/vscode-ext-commands
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/vscode-ext-commands -a gemini-cli -g -yNative Gemini CLI
gemini skills install https://github.com/github/awesome-copilot.git --scope workspace --path skills/vscode-ext-commands⚠ Installation uses the open-source skills CLI. Inspect the source and permissions before running the command.
Skill instructions
View source on GitHub ↗# 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 `category`, and don't need an `icon`, unless the command will be used in the Side Bar. * Side Bar commands: Its name follows a special pattern, starting with underscore (`_`) and suffixed with `#sideBar`, like `_extensionId.someCommand#sideBar` for instance. Must define an `icon`, and may or may not have some rule for `enablement`. Side Bar exclusive commands should not be visible in the Command Palette. Contributing it to the `view/title` or `view/item/context`, 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 correct `group` to be used. Also, it's a good practice to define the condition (`when`) for the new command is visible.