AutoGineer
Generated banner for Vscode Ext Commands
Generated logo for Vscode Ext Commands

Vscode Ext Commands

GitHubOfficialFirst committed by alefragnaniDistributed by GitHub

  • Skill
  • Guidelines
  • Software development
  • MIT
  • No issues found
Download ZIP

From 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
— the description by alefragnani

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides structured guidance for developers contributing commands to VS Code extensions. It covers essential configuration requirements such as command titles, naming conventions, visibility settings, and categorization. The documentation outlines specific patterns for standard commands versus those intended for the Side Bar, including requirements for icons, grouping, and visibility conditions.

What it does

  • Defines mandatory command attributes like titles.
  • Outlines naming conventions for standard and Side Bar commands.
  • Provides instructions for managing command visibility in the Command Palette.
  • Explains how to configure icons and grouping for Side Bar commands.
  • Details the use of enablement conditions for command visibility.

When to use it

  • When adding new functionality to a VS Code extension.
  • When updating existing command structures in an extension.
  • When determining the appropriate placement for a command in the UI.
  • When ensuring command naming follows established extension development patterns.

Advantages

  • Promotes consistency across VS Code extension command structures.
  • Clarifies the distinction between Command Palette and Side Bar command configurations.
  • Helps developers correctly implement command visibility and grouping.

Usage examples

“How should I name a command intended only for the Side Bar?”
The skill advises using a pattern starting with an underscore and suffixed with #sideBar, such as _extensionId.someCommand#sideBar.
“Do I need to include a category for all VS Code commands?”
Regular commands should define a category to ensure they are properly organized within the Command Palette.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/github/vscode-ext-commands/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip vscode-ext-commands.zip -d .agents/skills

Documentation by alefragnani

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.

Files

Requirements and compatibility

Written for: GitHub Copilot

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

First committed by
GitHub avatar of alefragnanialefragnani
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · skills/vscode-ext-commands · commit 797337f
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
alefragnani

AutoGineer is not affiliated with or endorsed by alefragnani or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download vscode-ext-commands.zip