Vscode Ext Commands
Add or refactor VS Code extension commands with correct titles, categories, Command Palette vs Side Bar naming, icons, and contribution metadata.
Overview
vscode-ext-commands is an agent skill for the Build phase that guides correct VS Code extension command contributions—titles, categories, Side Bar naming, icons, palette visibility, and menu placement.
Install
npx skills add https://github.com/github/awesome-copilot --skill vscode-ext-commandsWhat is this skill?
- Every command must define a title regardless of category or visibility
- Regular commands default to Command Palette with a category and optional Side Bar icon
- Side Bar commands use underscore prefix and #sideBar suffix and stay out of the palette when exclusive
- Documents view/title and view/item/context ordering, groups, and enablement rules
- Aligns with VS Code extension contribution guidelines and localization expectations
- Documents three command kinds: regular palette, Side Bar (_name#sideBar), and view/context placements
Adoption & trust: 8.8k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your VS Code extension commands are misnamed, missing categories or icons, or show up in the wrong UI surface because contribution rules are easy to get wrong.
Who is it for?
Solo extension authors updating package.json command tables who want agent reminders of underscore Side Bar IDs, icon rules, and menu group ordering.
Skip if: Teams building non-VS Code plugins, themes-only extensions with no commands, or users who need full extension packaging and marketplace publishing flows.
When should I use this skill?
You need to add or update commands in your VS Code extension following naming, visibility, localization, and menu contribution guidelines.
What do I get? / Deliverables
You get manifest-ready command definitions that follow VS Code patterns for palette, Side Bar, view titles, and context menus with sensible enablement.
- Corrected or new command entries in package.json
- Side Bar vs palette visibility and enablement rules documented in the change
- Menu group and ordering notes for view/title or view/item/context contributions
Recommended Skills
Journey fit
Build is primary because the skill guides package.json contributions and UX placement while you are authoring the extension—not distributing or operating it. integrations captures VS Code command contributions that wire editor UI, palettes, and view/toolbar contexts into your extension manifest.
How it compares
Use alongside general extension generators when you only need command contribution rules—not a full Yeoman or webview scaffold.
Common Questions / FAQ
Who is vscode-ext-commands for?
Indie developers and small teams writing VS Code extensions who need accurate command contribution metadata without re-reading the entire VS Code API docs.
When should I use vscode-ext-commands?
During Build integrations whenever you add or change commands in a VS Code extension—palette entries, Side Bar actions, or view toolbar buttons.
Is vscode-ext-commands safe to install?
It is documentation-only guidance for local manifest edits; review the Security Audits panel on this Prism page before installing any skill into your agent.
SKILL.md
READMESKILL.md - Vscode Ext Commands
# 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.