vscode-ext-commands

github/awesome-copilot · updated Apr 8, 2026

$npx skills add https://github.com/github/awesome-copilot --skill vscode-ext-commands
0 commentsdiscussion
summary

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

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.672 reviews
  • Hiroshi Li· Dec 28, 2024

    Keeps context tight: vscode-ext-commands is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Mia Patel· Dec 28, 2024

    Keeps context tight: vscode-ext-commands is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Noor Choi· Dec 28, 2024

    vscode-ext-commands fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ama Tandon· Dec 24, 2024

    I recommend vscode-ext-commands for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Ama Martin· Dec 16, 2024

    vscode-ext-commands has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Noor Abbas· Dec 4, 2024

    Registry listing for vscode-ext-commands matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Ama Johnson· Nov 23, 2024

    vscode-ext-commands fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Sakura Dixit· Nov 19, 2024

    vscode-ext-commands is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Mia Tandon· Nov 19, 2024

    vscode-ext-commands is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Noor Desai· Nov 15, 2024

    Useful defaults in vscode-ext-commands — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 72

1 / 8