Typing `//` no longer filters autocomplete to project skills whose frontmatter `name:` starts with `/` (regression in v2.1.160)

Summary

Project-level skills can set their frontmatter name: to begin with a slash (for example name: /list-ideas). This makes them show up in slash-command autocomplete as //list-ideas. We use a typed double-slash (//) as a quick way to filter the autocomplete menu down to just these project-scoped skills.

As of v2.1.160 this stopped working. Typing a single / still surfaces the //-prefixed skills, but typing // (two slashes) now returns no autocomplete suggestions at all. It still appears broken in v2.1.161 (current).

Background: the pattern

We set the name: field of each project skill to start with a slash so the skills group together under a // prefix in autocomplete. Example skill file:

---
name: /list-ideas
description: list all ideas in the ideas folder
---

With a folder of skills named this way (/list-ideas, /write-plan, /review-plan, /complete-plan-and-merge, etc.), typing // used to filter autocomplete to show only those project-scoped skills. It was a convenient way to see project skills at a glance without scrolling past built-in and global commands.

A full working example set lives in this public repo:

• Repo: https://github.com/DanielStormApps/claude-code-skills
• Example skill demonstrating the leading-slash name:: https://github.com/DanielStormApps/claude-code-skills/blob/main/skills/list-ideas/SKILL.md

Steps to reproduce

1. Create one or more project-level skills under .claude/skills/<skill>/SKILL.md whose frontmatter name: begins with a slash, for example name: /list-ideas.
2. Start Claude Code in that project.
3. In the prompt input, type a single /. The //-prefixed skills appear in the autocomplete menu (marked (project)).
4. Type a second / so the input reads //.

Expected

Typing // filters the autocomplete menu to show the project skills whose name: starts with / (the //list-ideas, //write-plan, etc. entries), the same set that appeared under a single /.

Actual

Typing // shows no autocomplete suggestions at all. The menu is empty. A single / still works correctly.

Environment

• Claude Code: first observed in v2.1.160, still present in v2.1.161 (current installed version)
• OS: macOS 26.5
• Shell: zsh

Possibly related

• #65047 (open): "Slash-command menu returns zero matches when query contains .". Same symptom shape (a punctuation character in the query yields zero autocomplete matches) bracketing the same version boundary. The // / leading-slash name: case described here does not appear to be covered there, but it may share a root cause in how the matcher normalizes the query versus the displayed command name.
• #38398: frontmatter name: prefix-stripping / using the name: field verbatim.
• #25837: a numeric skill name: breaking project-level slash autocomplete.
• #42809: a YAML-boolean skill name: breaking the slash command picker.
• #52257: an earlier skill-autocomplete substring-filter regression.

These suggest the autocomplete matcher is sensitive to non-standard name: values.

Screenshots

1. Typing a single / (working): the project skills appear as //-prefixed entries.

<img width="726" height="112" alt="Image" src="https://github.com/user-attachments/assets/c4bd21de-98c0-4ae1-b3ac-ef9a822ad4ed" />

2. Typing // (broken): no autocomplete suggestions appear.

<img width="659" height="102" alt="Image" src="https://github.com/user-attachments/assets/75e5253b-eb52-4671-853a-293813f7f57f" />