{"version":"2.1.284","anchor":"prompt-type-custom-commands-keep-their-full-name-as-an-alias","canonical_anchor":"prompt-type-custom-commands-keep-their-full-name-as-an-alias","heading":"More custom commands keep their full name as an alternative name","tier":"notice","area":"Slash Commands","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/prompt-type-custom-commands-keep-their-full-name-as-an-alias","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### More custom commands keep their full name as an alternative name\n\nMore custom prompt commands now keep their full name as an alias, which used to happen only for names that contain a colon\n\n**Unclear.** It is not clear which names pass the new check.\n\n**What**\n\nCustom commands and skills that expand into a prompt can be listed under a shorter name. The full name is sometimes kept as an alias, meaning an alternative name you can also type to run the command.\n\nBefore, the full name was kept only when it contained a colon. Now it is also kept when it passes a new check. This covers custom prompt commands that do not come from an MCP server (an external tool provider) and whose name does not clash with a built-in command.\n\n**Why**\n\nThis changes which names show up in autocomplete and which names Claude Code recognises when you type a command or skill.\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}