[FEATURE] Support personal/local slash commands in VS Code chat autocomplete

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

~/.claude/commands/*.md files are available to Claude as skills but do not appear in the VS Code extension's slash command autocomplete (/ trigger). Only plugin-installed commands (from ~/.claude/plugins/) appear in autocomplete.

Use case: Developers want personal workflow commands (e.g. internal ADO tooling, org-specific scripts) that should not be committed to a shared repo and should not be distributed as a plugin.

Expected behaviour: Commands in ~/.claude/commands/ should appear in VS Code chat autocomplete, matching the behaviour already present in the Claude Code CLI.

Workarounds tried:

~/.claude/commands/ — not indexed by VS Code
.claude/commands/ (project-level, gitignored) — not indexed
.github/skills/*/SKILL.md (gitignored) — not indexed
Local plugin in ~/.claude/plugins/marketplaces/local/ — not indexed

Proposed Solution

Allow ~/.claude/commands/*.md files to be indexed by the VS Code extension for slash command autocomplete, the same way they are already loaded as available skills in the CLI. This would give developers a supported, first-class location for personal commands that are:

Available across all projects (user-level, not project-level)
Never committed to any repository
Consistent with how the CLI already behaves
No new file format or directory structure would be required — the existing ~/.claude/commands/ convention and frontmatter format (description, argument-hint) are already in place.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

I work in an enterprise environment with internal Azure DevOps tooling. I have personal workflow commands (ticket analysis, release notes updates) that connect to our organisation's ADO instance. These commands contain organisation-specific defaults (URLs, project names, field references) that are not appropriate to share with the broader team or commit to the repository, but I want them available as slash commands in VS Code chat without having to remember exact syntax or type them out manually.

Additional Context

_No response_