skills.rest
aadorian
aadorianCOMMUNITY
Explore all skills by this author →
GitHub

tool-rename-deprecation

Preserve renamed tool references in legacy arrays during registration changes.

Updated Mar 28, 2026
Search Tags:#vscode#code review#refactoring#tooling#extensions#backward compatibility#legacy names
One-click install
npx skills add https://github.com/aadorian/VSCode_Readme --skill tool-rename-deprecation-aadorian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tool-rename-deprecation
Source: https://github.com/aadorian/VSCode_Readme/tree/main/education/engineering-tooling/github/copilot-skills/tool-rename-deprecation
Command: npx skills add https://github.com/aadorian/VSCode_Readme --skill tool-rename-deprecation-aadorian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents renamed tools and tool sets from breaking existing prompts, configurations, and saved references by enforcing backward compatibility during registration changes.

Core Features & Use Cases

  • Legacy Name Preservation: Ensures every renamed tool reference keeps its old name in the appropriate legacy array.
  • Tool Set Migration Safety: Handles tool set renames and moves so full tool paths continue to resolve correctly.
  • Consumer Validation: Checks prompt resolution, tool enablement, and auto-approval behavior so old names still work across the system.
  • Review and Regression Checks: Helps reviewers verify that stable identifiers stay unchanged and no legacy entries are removed.
  • Use Case: If a built-in tool is renamed, this Skill guides the update so existing users can keep using old prompts and settings without interruption.

Quick Start

Use this skill to review a tool rename and confirm the old reference name is added to the legacy array without changing the stable identifier.

Frequently Asked Questions about tool-rename-deprecation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rename a tool in VSCode without breaking existing prompts and configurations?▼

To rename a tool without breakage, add the old reference name to the appropriate legacy array while keeping the stable identifier unchanged. This ensures backward-compatible resolution so existing prompts, tool enablement, and auto-approval settings continue working.

What happens to saved references when an extension-contributed tool is renamed during a migration?▼

Saved references remain functional during a tool migration because the old name is preserved in a legacy array. This allows full tool paths to continue resolving correctly, ensuring consumer updates and prompt resolution do not interrupt existing users.

How do I verify backward compatibility when reviewing a tool rename in a pull request?▼

To verify backward compatibility during code review, check that stable identifiers remain unchanged and no legacy entries are removed. This validates that prompt resolution and auto-approval behavior still process old names correctly across the system.

Can I migrate a tool set to a new name without losing auto-approval settings?▼

Yes, migrating a tool set without losing auto-approval settings is possible by preserving the old name in a legacy array. This ensures backward-compatible resolution continues to work for consumer updates and tool enablement.

When do I need to update legacy arrays for renamed built-in tools?▼

You need to update legacy arrays for renamed built-in tools during registration changes and migrations. Verifying legacy arrays ensures that backward-compatible resolution continues to work for prompts, enablement, and auto-approval.

Related Skills

Explore More Software Engineering Skills→
shuyu-labsshuyu-labs
288

mcp-builder

Build MCP servers in TypeScript and Python with structured tool registration.

Official
Advanced
malwarebomalwarebo
5

tool-rename-deprecation

Preserve renamed tool references in legacy arrays for backward compatibility.

Community
Advanced
saitocosaitoco

review

Coordinate acceptance criteria verification and multi-perspective reviews on GitHub pull requests.

Official
Advanced
BertCalmBertCalm

version-guardian

Track XO_OX plugin parameter changes and generate migration scripts.

Community
Advanced