VS Code extension command contribution

SkillDev tools

Your AI can add and update commands in VS Code extensions while following official naming, visibility, and localization conventions. This skill supplies guidelines for contributing commands, drawn from VS Code extension development guidelines, libraries, and good practices.

Available today. Use it from your connected AI after setup.

After adding it, ask your AI to add or update a command in your VS Code extension, and it will follow the guidelines as it works.

Then ask your AI: use the VS Code extension command contribution skill

What your AI can do with it

  • Add new commands to VS Code extensions using the correct naming convention
  • Update existing commands so they follow visibility and localization guidelines
  • Set other relevant command attributes the way VS Code extension guidelines require
  • Apply VS Code extension development good practices and libraries when working on commands

What this skill tells your AI

The instructions your AI receives, as published by muromi-rikka/folder-alias in .agents/skills/vscode-ext-commands/SKILL.md and read by ahel’s review.

This skill helps you to contribute commands in VS Code extensions

When to use this skill

Use this skill when you need to:

  • Add or update commands to your VS Code extension

Instructions

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.

Signals

GitHub stars
26
Forks
10
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
vscode-ext-commands
Source
github.com/muromi-rikka/folder-alias