
Vscode Ext Commands
- 8.9k installs
- 37.1k repo stars
- Updated July 28, 2026
- github/awesome-copilot
vscode-ext-commands is an agent skill that Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Co.
About
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 --- name: vscode-ext-commands description: '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' --- # 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.
- VS Code extension command contribution
- Add or update commands to your VS Code extension
- --- name: vscode-ext-commands description: 'Guidelines for contributing commands in VS Code extensions.
- 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.
Vscode Ext Commands by the numbers
- 8,917 all-time installs (skills.sh)
- +21 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #89 of 16,659 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
vscode-ext-commands capabilities & compatibility
- Capabilities
- vs code extension command contribution · add or update commands to your vs code extension · name: vscode ext commands description: 'guid · must define an `icon`, and may or may not have s · side bar exclusive commands should not be visibl
- Use cases
- documentation
What vscode-ext-commands says it does
--- name: vscode-ext-commands description: 'Guidelines for contributing commands in VS Code extensions.
* 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.
npx skills add https://github.com/github/awesome-copilot --skill vscode-ext-commandsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 8.9k |
|---|---|
| repo stars | ★ 37.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | github/awesome-copilot ↗ |
What problem does vscode-ext-commands solve for developers using this skill?
Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, lib
Who is it for?
Developers who need vscode-ext-commands patterns described in the cached skill documentation.
Skip if: Skip when docs are empty or the task is outside the skill's documented scope.
When should I use this skill?
Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, lib
What you get
Actionable workflows and conventions from SKILL.md for vscode-ext-commands.
- Correct contributes.commands blocks in package.json
Files
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 anicon, 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#sideBarfor instance. Must define anicon, and may or may not have some rule forenablement. Side Bar exclusive commands should not be visible in the Command Palette. Contributing it to theview/titleorview/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 correctgroupto be used. Also, it's a good practice to define the condition (when) for the new command is visible.
Related skills
How it compares
Use vscode-ext-commands for manifest-level command metadata rather than general extension TypeScript architecture guidance.
FAQ
What does vscode-ext-commands do?
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 prac
When should I use 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 prac
Is vscode-ext-commands safe to install?
Review the Security Audits panel on this page before installing in production.