skills.rest
alexandereiseghohi
alexandereiseghohiCOMMUNITY
Explore all skills by this author →
GitHub

vscode-ext-commands

Enforce consistent command metadata and visibility rules for VS Code extensions.

Updated Jan 19, 2026
Search Tags:#vscode#localization#commands#extensions#naming-conventions#visibility#extension-development
One-click install
npx skills add https://github.com/alexandereiseghohi/ComicWise --skill vscode-ext-commands-alexandereiseghohi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vscode-ext-commands
Source: https://github.com/alexandereiseghohi/ComicWise/tree/main/skills/vscode-ext-commands
Command: npx skills add https://github.com/alexandereiseghohi/ComicWise --skill vscode-ext-commands-alexandereiseghohi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides guidelines for contributing commands in VS Code extensions, covering naming conventions, visibility rules, localization considerations, and best practices to ensure consistent UX and maintainability.

Core Features & Use Cases

  • Command metadata: enforce consistent titles, categories, and optional icons.
  • Visibility patterns: distinguish Regular vs Side Bar commands with explicit enablement and positioning rules.
  • Localization & accessibility: ensure support for multiple locales and accessible labels.
  • Use Case: when adding new commands to an extension, apply these guidelines to keep a cohesive command surface across the project.

Quick Start

Follow the provided guidelines to structure a new command contribution in your VS Code extension project, including defining a title, category, icon, and enablement conditions.

Frequently Asked Questions about vscode-ext-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure VS Code extension commands for consistent UX?▼

Standardize VS Code extension command contributions by enforcing consistent titles, categories, optional icons, and enablement rules. This ensures a cohesive command surface and maintainable extension UX across the project.

What is the difference between regular and side bar commands in VS Code extensions?▼

Regular and side bar commands differ by visibility patterns and explicit enablement rules. Side bar contributions require specific positioning rules to distinguish them from standard command palette entries.

How do I handle localization for VS Code extension command titles?▼

Handle localization for VS Code extension command titles by ensuring support for multiple locales and accessible labels. Following localization practices guarantees command titles are properly translated and accessible.

What naming conventions should I use for VS Code extension commands?▼

Use naming conventions for VS Code extension commands that enforce consistent titles and categories. Applying these guidelines when adding commands keeps a cohesive command surface across the project.

Can I customize command visibility and enablement rules in VS Code extensions?▼

You can customize command visibility and enablement rules in VS Code extensions. The guidelines enforce explicit enablement conditions and visibility patterns to distinguish command palette entries from side bar contributions.

Related Skills

Explore More Software Engineering Skills→
githubgithub
37.6k

vscode-ext-commands

Define structured guidelines for creating and validating VS Code extension commands.

Official
Basic
selfagencyselfagency

vscode-ext-commands

Standardize VS Code extension command definitions with titles, categories, and Side Bar patterns.

Community
Basic
githubgithub
37.6k

vscode-ext-localization

Localize VS Code extension resources across languages in package.json, walkthroughs, and code messages.

Official
Basic
beel-collabbeel-collab
1

vscode-ext-commands

Standardize and validate VS Code extension command contributions.

Community
Basic