claude-code - 💡(How to fix) Fix Feature request: customisable command palette showing built-in, skill, and user-defined 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#55628Fetched 2026-05-03 04:48:31
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
Timeline (top)
labeled ×2commented ×1
RAW_BUFFERClick to expand / collapse

Currently Claude Code has built-in slash commands (`/help`, `/clear`, etc.), skill commands (`/security-review`, `/ultrareview`, etc.), and user-definable keywords via `CLAUDE.md`. These three tiers exist but there's no unified way to discover or display them.

Proposed feature: A first-class command palette (e.g. triggered by `/commands` or a keyboard shortcut) that renders all available commands in a single view, with a Type column distinguishing Built-in / Skill / Custom. Custom commands would be defined in `CLAUDE.md` and picked up automatically.

This would make Claude Code significantly more approachable for new users (discoverability) while giving power users a clean way to document and surface their own workflow shortcuts. The `CLAUDE.md`-based customisation already works well — this just gives it a proper UI.

extent analysis

TL;DR

Implement a command palette feature to unify discovery and display of built-in, skill, and custom commands.

Guidance

  • Identify the technical requirements for creating a command palette, such as determining the data sources for built-in, skill, and custom commands.
  • Design a user interface for the command palette that includes a Type column to distinguish between command types.
  • Investigate how to automatically parse and integrate custom commands defined in CLAUDE.md into the command palette.
  • Consider implementing a trigger mechanism, such as a keyboard shortcut or /commands slash command, to access the command palette.

Notes

The proposed feature aims to improve discoverability and usability for new users, while also providing a clean way for power users to document and surface their workflow shortcuts.

Recommendation

Apply workaround: Implement a basic command palette feature to test and refine the concept before fully integrating it into the existing system.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Feature request: customisable command palette showing built-in, skill, and user-defined commands [1 comments, 2 participants]