VS Code Extension Commands

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.

Sidebar commands and context

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.