vscode-ext-commands

Adding a command to a VS Code extension requires defining a command contribution entry in your package.json. You must follow specific guidelines for naming conventions, visibility rules, and frontmatter metadata to ensure proper integration.

Naming conventions for VS Code extension commands require structured identifiers to prevent conflicts and ensure clarity. Following these guidelines helps maintain consistency across your extension and makes commands easier to discover in the Command Palette.

Localizing VS Code extension commands involves applying specific localization considerations when defining your command contributions. Structured guidelines help manage translations and ensure commands display correctly across different language packs.

Yes, contributing VS Code commands requires frontmatter metadata. The guidelines enforce that both a name and description are specified in the SKILL.md frontmatter to properly document the command definitions and their intended behavior.

Configuring command visibility and enablement for the VS Code Command Palette is supported through command contribution attributes. You can define rules to control when commands appear or are enabled, applying to both regular and side bar commands.