Skip to content

Feature request: group skills by category (folder) in the /skills menu #1162

Open

Description

@Wennington123

Summary

The /skills menu lists every skill in one flat list. I organize my 40+ user skills into category folders on disk (~/.commandcode/skills/android/, compose/, ponytail/, writing/) — discovery is recursive and works fine — but the menu has no way to show those groupings. It only groups by source (user/project/.agents). With many skills installed the picker becomes hard to scan.

Expected Behavior

/skills shows skills grouped by their on-disk category folder — one heading/collapsible section per intermediate folder under the skills root (e.g. android, compose, ponytail, writing) — so the menu stays navigable at 40+ skills.

Actual Behavior

/skills renders a single flat alphabetical list with (user)/(project)/[.agents] labels only. Folder categories are invisible: organizing skills into subfolders on disk changes nothing in the menu.

Steps to reproduce the issue

  1. Create nested category folders in ~/.commandcode/skills/ (e.g. android//SKILL.md) — recursive discovery picks them up, documented under "Nested skill folders".
  2. Open the /skills menu in an interactive session.
  3. Observe: one flat list; no grouping by folder/category anywhere in the UI.

Command Code Version

1.91.1

Operating System

Linux

Terminal/IDE

alacritty

Shell

fish

Session file (optional)

No response

Fix prompt (optional)

In the /skills picker, group entries by the skill's on-disk category folder (the path segment between the skills root and the skill's own directory, when one exists). Render a heading per category, keep a group for root-level skills, and preserve the existing (user)/(project)/[.agents] badges per row.

Additional context

Nested skill folders are already a documented feature ("Discovery is recursive"), but the /skills UI doesn't surface the folder structure. Today the only visual grouping in the menu comes from name prefixes (android-, compose-, ...).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions