---
id: ssh-vscode-ext-commands
name: "vscode-ext-commands"
url: https://skills.yangsir.net/skill/ssh-vscode-ext-commands
author: github
domain: ai-dev-tools-workflow
tags: ["vs-code-extensions", "extension-development", "command-palette", "developer-tools", "javascript/typescript"]
install_count: 8700
rating: 4.50 (298 reviews)
github: https://github.com/github/awesome-copilot
---

# vscode-ext-commands

> 提供VS Code扩展中贡献命令的指南，包括命名约定、可见性和本地化等属性。

**Stats**: 8,700 installs · 4.5/5 (298 reviews)

## Before / After 对比

### 规范VS Code扩展命令提升用户体验

## Readme

# 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.


---
*Source: https://skills.yangsir.net/skill/ssh-vscode-ext-commands*
*Markdown mirror: https://skills.yangsir.net/api/skill/ssh-vscode-ext-commands/markdown*