Feature Request: Skills should have the same slash autocomplete as commands

Resolved 💬 3 comments Opened Apr 15, 2026 by YuInoue19 Closed Apr 18, 2026

Feature Request

Problem

When typing / in the CLI, custom commands (.claude/commands/*.md) appear as autocomplete suggestions, but custom skills (.claude/skills/<name>/SKILL.md) do not.

Since the official documentation states "Custom commands have been merged into skills," users expect the same UX for both. Currently, the only way to get / autocomplete is to use the legacy commands format.

Proposed Solution

Show skills in the / autocomplete list, just like commands. When a user types /h, a skill named handover should appear as a suggestion.

Why This Matters

  • Consistency: Commands and skills are documented as equivalent, but the UX differs.
  • Non-English-speaking users: Typing full English command names is a significant burden. Autocomplete suggestions make the tool far more accessible for users who are not native English speakers or typists.
  • Non-engineer users: Claude Code is increasingly used by non-technical users. Autocomplete lowers the barrier — users don't need to memorize exact command names.

Current Workaround

Place the file in .claude/commands/ instead of .claude/skills/ to get autocomplete, but this means giving up skill-only features (auto-trigger, allowed-tools, context: fork, etc.).

Environment

  • Claude Code CLI on macOS
  • Skills placed at ~/.claude/skills/<name>/SKILL.md

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗