Skip to main content
Back to the directory
microsoft/vscodeSoftware EngineeringFrontend and Design

tool-rename-deprecation

When a tool or tool set reference name is changed, the old name must always be added to the deprecated/legacy array so that existing prompt files, tool configurations, and saved references continue to resolve correctly.

SkillJury keeps community verdicts, source metadata, and external repository signals in separate lanes so ranking data never pretends to be a review.

SkillJury verdict
Pending

No approved reviews yet

Would recommend
Pending

Waiting on enough review volume

Install signal
686

Weekly or total install activity from catalog data

Sign in to review
0 review requests
Install command
npx skills add https://github.com/microsoft/vscode --skill tool-rename-deprecation
SkillJury does not have enough approved reviews to publish a community verdict yet. Source metadata and repository proof are still available above.
SkillJury Signal Summary

As of Apr 30, 2026, tool-rename-deprecation has 686 weekly installs, 0 community reviews on SkillJury. Community votes currently stand at 0 upvotes and 0 downvotes. Source: microsoft/vscode. Canonical URL: https://skills.sh/microsoft/vscode/tool-rename-deprecation.

Security audits
Gen Agent Trust HubPASS
SocketPASS
SnykPASS
About this skill
When a tool or tool set reference name is changed, the old name must always be added to the deprecated/legacy array so that existing prompt files, tool configurations, and saved references continue to resolve correctly. Run this skill on any change to built-in tool or tool set registration code to catch regressions: Determine whether you are renaming a tool or a tool set , and where it is registered: Critical: For extension-contributed tools, the name field in package.json is mapped to id on IToolData (see languageModelToolsContribution.ts line id: rawTool.name ). It is also used for activation events ( onLanguageModelTool: ). Never rename the name field — only rename toolReferenceName . Verify the old toolReferenceName value appears in legacyToolReferenceFullNames . Don't assume it's already there — check the actual array contents. If the old name is already listed (e.g., from a previous rename), confirm it wasn't removed. If it's not there, add it.

Source description provided by the upstream listing. Community review signal and install context stay separate from this narrative layer.

Community reviews

Latest reviews

No community reviews yet. Be the first to review.

Browse this skill in context
FAQ
What does tool-rename-deprecation do?

When a tool or tool set reference name is changed, the old name must always be added to the deprecated/legacy array so that existing prompt files, tool configurations, and saved references continue to resolve correctly.

Is tool-rename-deprecation good?

tool-rename-deprecation does not have approved reviews yet, so SkillJury cannot publish a community verdict.

Which AI agents support tool-rename-deprecation?

tool-rename-deprecation currently lists compatibility with Skills CLI.

Is tool-rename-deprecation safe to install?

tool-rename-deprecation has been scanned by security audit providers tracked on SkillJury. Check the security audits section on this page for detailed results from Socket.dev and Snyk.

What are alternatives to tool-rename-deprecation?

Skills in the same category include grimoire-morpho-blue, conversation-memory, second-brain-ingest, zai-tts.

How do I install tool-rename-deprecation?

Run the following command to install tool-rename-deprecation: npx skills add https://github.com/microsoft/vscode --skill tool-rename-deprecation

Related skills

More from microsoft/vscode

Related skills

Alternatives in Software Engineering