Skip to main content
Back to the directory
github/awesome-copilotSoftware EngineeringFrontend and Design

vscode-ext-commands

VS Code extension command contribution patterns and naming conventions.

SkillJury keeps community verdicts, source metadata, and external repository signals in separate lanes so ranking data never pretends to be a review.

SkillJury verdict
Pending

No approved reviews yet

Would recommend
Pending

Waiting on enough review volume

Install signal
8

Weekly or total install activity from catalog data

Sign in to review
0 review requests
Install command
npx skills add https://github.com/github/awesome-copilot --skill vscode-ext-commands
SkillJury does not have enough approved reviews to publish a community verdict yet. Source metadata and repository proof are still available above.
SkillJury Signal Summary

As of Apr 30, 2026, vscode-ext-commands has 8 weekly installs, 0 community reviews on SkillJury. Community votes currently stand at 0 upvotes and 0 downvotes. Source: github/awesome-copilot. Canonical URL: https://skills.sh/github/awesome-copilot/vscode-ext-commands.

Security audits
Gen Agent Trust HubPASS
SocketPASS
SnykPASS
About this skill
VS Code extension command contribution patterns and naming conventions. This skill helps you to contribute commands in VS Code extensions Use this skill when you need to: 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.

Source description provided by the upstream listing. Community review signal and install context stay separate from this narrative layer.

Community reviews

Latest reviews

No community reviews yet. Be the first to review.

Browse this skill in context
FAQ
What does vscode-ext-commands do?

VS Code extension command contribution patterns and naming conventions.

Is vscode-ext-commands good?

vscode-ext-commands does not have approved reviews yet, so SkillJury cannot publish a community verdict.

Which AI agents support vscode-ext-commands?

vscode-ext-commands currently lists compatibility with Skills CLI.

Is vscode-ext-commands safe to install?

vscode-ext-commands has been scanned by security audit providers tracked on SkillJury. Check the security audits section on this page for detailed results from Socket.dev and Snyk.

What are alternatives to vscode-ext-commands?

Skills in the same category include grimoire-morpho-blue, conversation-memory, second-brain-ingest, zai-tts.

How do I install vscode-ext-commands?

Run the following command to install vscode-ext-commands: npx skills add https://github.com/github/awesome-copilot --skill vscode-ext-commands

Related skills

More from github/awesome-copilot

Related skills

Alternatives in Software Engineering