VS Code extension command contribution patterns and naming conventions.
Works with
Defines two command types: regular commands (accessible in Command Palette with required category and title ) and Side Bar commands (prefixed with underscore and suffixed with #sideBar , requiring an icon )
Side Bar commands support visibility rules via enablement and when conditions, with positioning controlled through group and order attributes
All commands must define a title ; icons are optional for regular c
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.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionvscode-ext-commandsExecute the skills CLI command in your project's root directory to begin installation:
Fetches vscode-ext-commands from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate vscode-ext-commands. Access via /vscode-ext-commands in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28.7K
stars
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
github/awesome-copilot
github/awesome-copilot
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
Keeps context tight: vscode-ext-commands is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: vscode-ext-commands is the kind of skill you can hand to a new teammate without a long onboarding doc.
vscode-ext-commands fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend vscode-ext-commands for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
vscode-ext-commands has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for vscode-ext-commands matched our evaluation — installs cleanly and behaves as described in the markdown.
vscode-ext-commands fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
vscode-ext-commands is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
vscode-ext-commands is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in vscode-ext-commands — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 72