vscode-ext-commands

Standardize VS Code extension command definitions with titles, categories, and Side Bar patterns.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/selfagency/agentsy --skill vscode-ext-commands-selfagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vscode-ext-commands
Source: https://github.com/selfagency/agentsy/tree/main/.agents/skills/vscode-ext-commands
Command: npx skills add https://github.com/selfagency/agentsy --skill vscode-ext-commands-selfagency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents inconsistent or non-compliant VS Code extension command definitions by standardizing required fields, naming patterns, and visibility rules so commands integrate cleanly with VS Code UX.

Core Features & Use Cases

  • Command definition requirements: Ensures every command defines a title and follows the expected structure for how commands appear and behave.
  • Category and palette behavior guidance: Clarifies how regular commands should be exposed to the Command Palette and when icons are needed.
  • Side Bar command conventions: Defines the underscore naming pattern, icon requirement, and guidance for ordering and conditional visibility for Side Bar-only commands.

Quick Start

Use this skill to add a new command by specifying its title, category, and—if it is a Side Bar command—its underscore-prefixed name and required icon.

Frequently Asked Questions about vscode-ext-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a VS Code extension command to the Command Palette?

To add a VS Code extension command to the Command Palette, you must define a title and a category for the command. This standardizes command metadata and ensures consistent visibility and UX integration within the palette.

What is the naming convention for VS Code Side Bar commands?

VS Code Side Bar commands must follow the _<extensionId>.<command>#sideBar naming pattern. This convention requires an icon and appropriate when or enablement rules to manage conditional visibility and ordering within the Side Bar.

Do VS Code extension commands require an icon?

VS Code extension commands require an icon if they are defined as Side Bar commands. Regular commands do not strictly require icons but must include a title and a category to avoid invalid command metadata.

Why are my VS Code extension commands showing inconsistent UX?

Inconsistent VS Code extension command UX occurs when command definitions lack standardized metadata. Ensuring every command has a title, a category, and correct enablement conditions standardizes their behavior and integration cleanly.

What's the best way to structure VS Code extension command metadata?

The best way to structure VS Code extension command metadata is to standardize required fields, naming patterns, and visibility rules. Ensure every command defines a title, regular commands define a category, and Side Bar commands use the underscore pattern.