Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Feature Request: Skills should have the same slash autocomplete as commands [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48355•Fetched 2026-04-16 07:02:32
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
YuInoue19YuInoue19
Participants
github-actions[bot]github-actions[bot]YuInoue19YuInoue19
Timeline (top)
labeled ×4commented ×1

Root Cause

  • 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.

Fix Action

Fix / Workaround

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.

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.).

RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

Update the autocomplete logic to include custom skills from the .claude/skills/ directory.

Guidance

  • Review the current implementation of autocomplete suggestions to identify why custom skills are not being included.
  • Verify that the file path and naming conventions for custom skills (.claude/skills/<name>/SKILL.md) are correctly registered in the autocomplete system.
  • Consider modifying the autocomplete function to recursively search for SKILL.md files within the .claude/skills/ directory and its subdirectories.
  • Test the updated autocomplete feature with various skill names and prefixes to ensure it works as expected.

Example

No code example is provided due to the lack of specific implementation details in the issue.

Notes

The solution may require changes to the Claude Code CLI's internal logic for handling custom skills and autocomplete suggestions. The proposed solution should ensure that custom skills are treated equivalently to custom commands in terms of autocomplete functionality.

Recommendation

Apply a workaround by modifying the autocomplete logic to include custom skills, as the issue implies that the current implementation is inconsistent with the documented behavior.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#batch processing#GPU compatibility#latency issue#model loading#dependency error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING