VS Code Extension Commands

Guidance for clearly named, visible, and localizable commands in Visual Studio Code extensions.

The VS Code Extension Commands skill is published in GitHub's official github/awesome-copilot repository. It helps extension developers design commands consistently and describe them correctly in a Visual Studio Code extension manifest. According to the provider, the skill focuses on naming, visibility, localization, and other relevant attributes of extension commands. It is not an executable extension and does not replace the VS Code API. Instead, it is a concise editorial knowledge source that a coding agent can consult while planning, implementing, or reviewing extension contributions.

The problem this skill addresses

A command can work technically and still be difficult to find, inconsistently labeled, or exposed in the wrong editor location. The skill directs attention first to a title field that should always be defined. This gives every command a human-readable label regardless of its category, visibility, or placement. For regular commands, the source also describes a category and the default expectation that they are accessible through the Command Palette. These conventions help an agent inspect package.json contributions and review diffs without prescribing a particular extension architecture or programming language.

A dedicated part of the source covers commands intended exclusively for a sidebar. It specifies a naming pattern with a leading underscore and the #sideBar suffix. Such commands need an icon and should not also be exposed through the Command Palette when they are truly sidebar-only. For view/title and view/item/context contributions, the skill highlights the importance of group, order, and position relative to neighboring controls. A suitable when condition can describe when a command should be visible. These rules give an agent a practical way to check whether a contribution explains its intended interaction context rather than merely registering a command identifier.

Practical use in development

Use this skill when adding a new command, updating existing contribution points, or preparing a review of extension metadata. An agent can clarify the command's audience and location, compare title, category, icon, enablement, when, and group with that context, and then check naming consistency across related commands. The guidance does not replace tests. The extension still needs to be exercised with the supported VS Code versions, menus, activation behavior, and accessibility expectations. The official VS Code documentation notes that invoking a command can emit an onCommand activation event, so activation strategy and runtime registration must be reviewed through the normal API and test process.

Boundaries and security

The skill does not edit files by itself and does not grant an agent permissions. Extension changes can nevertheless execute code, read workspace files, or contact external services. Review generated changes in a controlled worktree, use narrowly scoped permissions, and confirm actions that have external side effects. Menu visibility is not an authorization mechanism: when and enablement improve user experience, but they do not replace access control. Consult the official VS Code reference for version-dependent details about commands, menus, icons, activation, and localization. GitHub identifies the awesome-copilot repository as MIT licensed. Its star count is a time-bound repository popularity signal, not evidence of the quality, security, or maintenance of this individual skill path.

Catalog classification

The content belongs in Coding and can guide several agentic coding environments because it is instructional rather than tied to one runtime. For exact manifest syntax, icon definitions, menu locations, and activation events, the official VS Code documentation remains the authoritative technical reference. This entry does not state fixed prices because terms for GitHub, VS Code, and any connected development environment are separate from the catalog record. Treat the skill as a review aid: understand the intended user experience, validate the manifest, run the extension tests, and inspect the resulting command in the real editor before release.

Installation instructions

What This Skill Is About

VS Code Extension Commands is a skill from GitHub's official Awesome Copilot repository, which provides a curated collection of instructions, prompts, and skills for working with GitHub Copilot. According to the provider, this particular skill helps developers correctly define commands within VS Code extensions. It summarizes the naming conventions, visibility rules, localization requirements, and other relevant attributes mandated by the official VS Code extension development guidelines. The skill therefore does not target end users of an extension but people who themselves build or maintain extensions for the Visual Studio Code editor while working alongside an AI-assisted tool such as Copilot.

When the Skill Applies

The skill activates whenever a task involves adding or updating commands in a VS Code extension. That could mean defining a new command in the package.json manifest file, adjusting an existing command to new visibility rules, or restructuring a set of commands for the side bar. Unlike a general coding tool, this skill does not deliver generic programming knowledge; instead it provides very specific, VS-Code-typical conventions that also show up in Microsoft's official sample extensions and the extension API documentation.

Core Rules the Skill Conveys

According to the guidance stored in the skill, every VS Code command must define a title regardless of its category, visibility, or location. Regular commands should, by default, be reachable through the Command Palette, need a category, and generally do not need an icon unless they also appear in the side bar. Commands meant to be visible exclusively in the side bar follow their own naming pattern with a leading underscore and a side-bar suffix; such commands mandatorily need an icon but must not also show up in the Command Palette. When a command is placed in a context menu such as the view title bar, its relative order compared to other commands and a sensible visibility condition must additionally be defined.

Practical Value for Extension Developers

The value of this skill lies in an AI assistant no longer suggesting only syntactically correct but also stylistically consistent code for command definitions during extension development. Especially in larger extensions with many commands, inconsistent naming patterns, missing categories, or commands that accidentally appear both in the side bar and the Command Palette otherwise arise easily, degrading the user experience. An assistant aware of these conventions can avoid such inconsistencies early on or flag them during a review before an extension is published.

Step 1: Prerequisites and Context

To use the skill meaningfully you need an existing or newly created VS Code extension project along with a Copilot-capable editor in which the Awesome Copilot repository is wired in as a source for skills, prompts, or instructions. Since this is, according to the provider, a collection of community- and Microsoft-curated content, it is worth checking the actual skill file in the repository and cross-referencing it with the official VS Code extension API documentation before production use, in case details such as the manifest schema or visibility attributes have changed with newer VS Code releases.

Limits of the Skill

Importantly, this skill sticks strictly to command definitions and does not provide comprehensive guidance on overall extension architecture, activation events, or Marketplace publishing. Anyone planning a complete extension from scratch will additionally need the general VS Code extension documentation. The skill also does not replace a manual review of the resulting package.json, because schema changes in future VS Code releases can make individual patterns described in the skill outdated, so checking the current official documentation before each release remains advisable.

Free
Provider
GitHub
License
MIT
Last reviewed
09.09.2026

Repository and documentation

Categories

Compatible with

Claude Code Codex Cursor