## Bug Description When the `/voice` command is entered, it can trigger plugin-registered skills instead of activating the built-in voice mode. In my case, the `impeccable:adapt` skill was triggered instead of voice mode activating. ## Steps to Reproduce 1. Install a plugin that registers skills/commands (e.g., [impeccable](https://github.com/pbakaus/impeccable)) 2. Type `/voice` to activate voice mode 3. Observe that a plugin skill is triggered instead of voice mode ## Expected Behaviour T

/voice command triggers plugin skills instead of activating voice mode

Status Fixed / completed

Maintainer reply None cached

Activity 4 comments · opened Mar 12, 2026 · closed Mar 13, 2026

Bug Description

When the /voice command is entered, it can trigger plugin-registered skills instead of activating the built-in voice mode. In my case, the impeccable:adapt skill was triggered instead of voice mode activating.

Steps to Reproduce

Install a plugin that registers skills/commands (e.g., impeccable)
Type /voice to activate voice mode
Observe that a plugin skill is triggered instead of voice mode

Expected Behaviour

The built-in /voice command should take priority over plugin-registered skills and activate voice mode.

Actual Behaviour

A plugin skill (impeccable:adapt in this case) was triggered instead of voice mode. The adapt skill's body text contains the word "voice" (in a list of input methods), which may be contributing to the incorrect match.

Environment

OS: macOS Sequoia 15.6
Shell: zsh
Plugin: impeccable v1.0.0

Analysis

The impeccable plugin registers commands correctly via standard frontmatter (e.g., name: adapt). There are no aliases or fuzzy triggers defined. The conflict appears to be in Claude Code's command/skill resolution system — built-in commands should take priority over plugin skills, especially when there is no name match.

View original on GitHub ↗

4 Comments

davemac · 7 months ago

Additional Context

The issue is specifically in the autocomplete/fuzzy matching dropdown. When typing /voice, the autocomplete suggests /adapt (impeccable) because the word "devices" in the adapt skill's description partially matches "voice" via fuzzy matching.

The autocomplete dropdown appears immediately and if the user presses Enter, it selects the plugin skill instead of the built-in /voice command.

Expected: Built-in commands like /voice should appear first in autocomplete results (or the fuzzy matcher should prioritise command names over description text).

github-actions[bot] · 7 months ago

Found 3 possible duplicate issues:

This issue will be automatically closed as a duplicate in 3 days.

If your issue is a duplicate, please close it and 👍 the existing issue instead
To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

davemac · 7 months ago

Update: /voice command not registered

On v2.1.74 (latest), after bypassing the autocomplete with Escape, /voice returns:

Unknown skill: voice

So this is actually two issues:

The status line announces "Voice mode is now available · /voice to enable" but the /voice command is not actually registered as a built-in command in v2.1.74
The autocomplete fuzzy matching suggests plugin skills (e.g. /adapt from impeccable) when typing /voice, because it matches against description text containing "devices"

The /voice command appears to be announced in the UI but not yet functional.

github-actions[bot] · 6 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.