What problem does it solve? Renaming a built-in tool's toolReferenceName or a tool set's referenceName silently breaks existing prompt files, tool configurations, and auto-approval settings that reference the old name. This Skill ensures every rename adds the old name to the legacy arrays so saved references keep resolving. ## Core Features & Use Cases - Legacy Name Registration: Guides adding old names to legacyToolReferenceFullNames for tools and legacyFullNames for tool sets, including toolSet/toolName paths for moved tools. - Stable ID Protection: Flags changes to the package.json name field or TypeScript id field, which must never change since they drive activation events and tool invocation. - Consumer Verification: Checks that prompt file resolution, tool enablement maps, and auto-approval settings all respect legacy names after a rename. - Use Case: When reviewing a PR that renames a tool from 'todos' to 'todo', run this Skill to confirm 'todos' was added to legacyToolReferenceFullNames and that no legacy entries were removed. ## Quick Start Review this pull request that renames a built-in tool and verify the old reference name was added to the legacy names array.