{"version":"2.1.304","anchor":"plugin-validate-flags-shipped-command-names","canonical_anchor":"plugin-validate-flags-shipped-command-names","heading":"Plugin validation now reports commands that reuse built-in names","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/plugin-validate-flags-shipped-command-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Plugin validation now reports commands that reuse built-in names\n\nValidating a plugin now reports an error for each command it registers under a name Claude Code already ships\n\n**What**\n\nPlugin validation is the check Claude Code runs to find problems in a plugin. It now reports an error for every command a plugin module registers under a name that Claude Code already ships.\n\nBefore, such commands were quietly filtered out and no error was shown. Claude Code still refuses to register these commands with `$.command.register`, and the hook that tries to register one is skipped. A hook is a piece of a plugin that runs at a set point.\n\n**Why**\n\nPlugin authors now see the name clash as a validation error. Before, the command simply went missing with no explanation.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}