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 patterns and naming conventions.
Defines two command types: regular commands (accessible in Command Palette with required category and title ) and Side Bar commands (prefixed with underscore and suffixed with #sideBar , requiring an icon ) Side Bar commands support visibility rules via enablement and when conditions, with positioning controlled through group and order attributes All commands must define a title ; icons are optional for regular commands but required for Side Bar commands Emphasizes best practices including Command Palette visibility control, localization support, and conditional rendering based on extension state
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotDeclared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars38.8K
LicenseLICENSE
Default branchmain
Open issues21
Status
Active
Skill metadata
Parsed from SKILL.md frontmatter.
Declared agentsgithub-copilot
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md1,545 B
docsSUMMARY.md252 B
History
First seen on skills.sh
First recorded snapshot · 9,100 installs
SKILL.md
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.
