Skip to content
Skillpedia
Deploy & cloud (DevOps)40k · #5415

vscode-ext-commands

Helps your agent add new commands in VS Code extensions. It follows guidelines for naming, visibility, and localizing commands correctly.

What it does

This tool helps you add or update commands in VS Code extensions. It ensures commands follow VS Code's rules and best practices.

When to use it

  • ✓Adding a new command to your VS Code extension.
  • ✓Updating an existing command in your extension.
  • ✓Ensuring your commands follow VS Code conventions.

Example of what to ask your AI

“How do I add a new command to my VS Code extension following best practices?”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/github/awesome-copilot/blob/main/skills/vscode-ext-commands/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/github/awesome-copilot/blob/main/skills/vscode-ext-commands/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool checks if commands have a title, follow naming patterns, and are visible correctly. It helps organize commands for the Command Palette or the VS Code Side Bar.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add github/awesome-copilot --skill vscode-ext-commands

Or download just the file:

curl -L https://raw.githubusercontent.com/github/awesome-copilot/main/skills/vscode-ext-commands/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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.

FAQ

What is a 'command' in VS Code?

A command is an action you can perform within VS Code, like opening a file, formatting code, or running a specific function from an extension.

What is the 'Command Palette'?

It's a search box in VS Code where you can type to quickly find and execute commands.

What are 'Side Bar' commands?

These are commands that appear in specific locations of the VS Code Side Bar, like buttons or menus, and not in the general Command Palette.

Details

Original description by the author

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

repo: github/awesome-copilot

Popularity

GitHub stars
40k
Ranking position
#5415
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills