/voice command triggers plugin skills instead of activating voice mode
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
/voiceto 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.
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗