PaperclipOrg
Claude Agent Skill · by Github

Vscode Ext Commands

Handles the specific conventions for contributing commands to VS Code extensions, covering the distinction between regular Command Palette commands and Side Bar

Install
Terminal · npx
$npx skills add https://github.com/github/awesome-copilot --skill vscode-ext-commands
Works with Paperclip

How Vscode Ext Commands fits into a Paperclip company.

Vscode Ext Commands drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md21 lines
Expand
---name: vscode-ext-commandsdescription: '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. * 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.