Problem
The plugin registers a slash command named doctor, which shadows Claude Code's built-in /doctor diagnostic command. When taskyou-os is enabled, typing /doctor invokes taskyou-os:doctor instead of the built-in.
Claude Code has no namespace-escape syntax (e.g. /builtin:doctor) — plugin commands take precedence and there is no way to reach the built-in without disabling the plugin.
Reproduction
- Install/enable the
taskyou-os plugin in Claude Code
- Type
/doctor
- Observe:
taskyou-os:doctor runs instead of the built-in diagnostic
Impact
Users lose access to Claude Code's built-in /doctor (used to diagnose CLI / installation / MCP / auth issues) for as long as the plugin is enabled. The workaround is to disable the plugin, run /doctor, then re-enable — friction every time something needs diagnosing.
Suggested fix
Rename the plugin's command to a namespaced/qualified form that won't collide with built-ins, e.g.:
/taskyou-doctor
/taskyou-os-doctor
/gm-doctor
The same caution applies to any other generic names the plugin uses (/help, /status, /clear, etc.) — best practice is for plugin commands to carry a plugin-specific prefix.
Thanks!
Problem
The plugin registers a slash command named
doctor, which shadows Claude Code's built-in/doctordiagnostic command. Whentaskyou-osis enabled, typing/doctorinvokestaskyou-os:doctorinstead of the built-in.Claude Code has no namespace-escape syntax (e.g.
/builtin:doctor) — plugin commands take precedence and there is no way to reach the built-in without disabling the plugin.Reproduction
taskyou-osplugin in Claude Code/doctortaskyou-os:doctorruns instead of the built-in diagnosticImpact
Users lose access to Claude Code's built-in
/doctor(used to diagnose CLI / installation / MCP / auth issues) for as long as the plugin is enabled. The workaround is to disable the plugin, run/doctor, then re-enable — friction every time something needs diagnosing.Suggested fix
Rename the plugin's command to a namespaced/qualified form that won't collide with built-ins, e.g.:
/taskyou-doctor/taskyou-os-doctor/gm-doctorThe same caution applies to any other generic names the plugin uses (
/help,/status,/clear, etc.) — best practice is for plugin commands to carry a plugin-specific prefix.Thanks!