
Tool Rename Deprecation
Run this whenever you're renaming a tool or tool set identifier in VS Code's language model tools API to ensure old references keep working. It enforces the pattern of adding the previous name to legacyToolReferenceFullNames or legacyFullNames arrays so existing prompt files, configs, and auto-approval settings don't break. The skill walks through the distinction between stable IDs (never change) and reference names (can change with proper deprecation), checks all the places tool names get resolved, and includes real examples like runInTerminal being renamed from runCommands/runInTerminal. It's basically a checklist to prevent the kind of regression where someone's auto-approval restriction silently stops working because you forgot to preserve the old name in the lookup chain.
- skills.sh installs
- 2.6K
- GitHub stars
- 195.3K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add microsoft/vscode --skill tool-rename-deprecation --agent claude-codeInstalls into .claude/skills of the current project.
Files
Run this whenever you're renaming a tool or tool set identifier in VS Code's language model tools API to ensure old references keep working. It enforces the pattern of adding the previous name to legacyToolReferenceFullNames or legacyFullNames arrays so existing prompt files, configs, and auto-approval settings don't break. The skill walks through the distinction between stable IDs (never change) and reference names (can change with proper deprecation), checks all the places tool names get resolved, and includes real examples like runInTerminal being renamed from runCommands/runInTerminal. It's basically a checklist to prevent the kind of regression where someone's auto-approval restriction silently stops working because you forgot to preserve the old name in the lookup chain.
Browse the repository on GitHubSponsors
Details
- Repository
- github.com/microsoft/vscode
- First seen
- Apr 16, 2026