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

Resolved 💬 11 comments Opened Dec 20, 2025 by PaulRBerg 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 ↗

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