[FEATURE] Separate skills and slash commands in /context output

Status Closed — not planned
Maintainer reply None cached
Activity 11 comments · opened Dec 20, 2025 · closed Feb 26, 2026

Problem

When using the /context command, skills and slash commands are bundled together under a single category called "Skills and slash commands". This makes it harder to understand what's loaded because skills and slash commands serve different purposes:

  • Skills are loaded contextually based on trigger descriptions and provide domain knowledge
  • Slash commands are user-invocable actions that execute specific workflows

Combining them obscures the distinction and makes it less clear what each item does.

<img width="390" height="333" alt="Image" src="https://github.com/user-attachments/assets/96fee935-c500-4277-994c-3ea0b9909aa0" />

Proposed solution

Split "Skills and slash commands" into two separate categories in the /context output:

  • Skills - Lists loaded skills with their trigger descriptions
  • Slash commands - Lists available slash commands

This would make the context breakdown clearer and help users understand what's available at a glance.

Priority

Medium

Category

CLI commands and flags

View original on GitHub ↗

10 Comments

mrgoonie · 7 months ago

yes, totally agree!

<img width="1395" height="854" alt="Image" src="https://github.com/user-attachments/assets/598ca982-44f8-46a3-8753-d7013f227ef7" />

merging commands and skills doesn't seem to be a good idea, it's killing my eyes...

it also brings terminal flashing issue back when starting CC in a small window

proposal

using another symbol for skills, such as # -> better to invoke multiple skills

prompt will be like:

#skill1 #skill2 #skill3 implement this feature bla bla...

by doing this we can invoke skills with slash commands as well

/brainstorm how to implement this feature bla bla... #brainstorm #critical-thinking #problem-solving #researching
PaulRBerg · 7 months ago
using another symbol for skills, such as #

That's a great idea

thieung · 7 months ago

Agree with @mrgoonie , using # for skill is good idea

huyhoangnhh98 · 7 months ago

Please update by following @mrgoonie. This is a good idea.

hieubui2409 · 7 months ago

Upvote

hieutv-dng · 7 months ago

Up

PaulRBerg · 7 months ago

Opened a separate issue for @mrgoonie's # proposal because I still want this issue about the /context command to remain open - it's a separate concern.

Please upvote https://github.com/anthropics/claude-code/issues/17647 if you want skills to be invoked via # instead of /

github-actions[bot] · 6 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

github-actions[bot] · 6 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

github-actions[bot] · 5 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

Showing cached comments. Read the full discussion on GitHub ↗