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

Resolved 💬 4 comments Opened Jan 8, 2026 by PaulRBerg Closed Feb 22, 2026

Problem

When running /context, plugins, plugin slash commands, and plugin skills all appear bundled together under a single "Plugin" category. This makes it difficult to distinguish between:

  • Slash commands from plugins (user-invoked with /command)
  • Skills from plugins (model-invoked based on context)

Currently the output shows:

Skills and slash commands
└ Plugin
  └ Hook Development
  └ Command Development
  └ ...

This conflates two distinct invocation models.

Proposed solution

Display plugin components in dedicated categories that match the user/project pattern:

  • Plugin slash commands - for user-invoked /commands from plugins
  • Plugin skills - for model-invoked skills from plugins

This would provide clearer visibility into what's available and how each item is invoked.

Alternatives considered

None - the current bundled display is the only option.

Priority

Medium

Category

CLI commands and flags

Related

See https://github.com/anthropics/claude-code/issues/14835 for related discussion on skills vs slash commands distinction.

View original on GitHub ↗

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