skills.rest
THRISHAL12345
THRISHAL12345COMMUNITY
Explore all skills by this author →
Website𝕏@DomaThrishalGitHub

tool-rename-deprecation

Preserve legacy tool reference names during TypeScript tool registration renames.

Updated Aug 23, 2026
Search Tags:#vscode#code review#refactoring#tooling#backward compatibility#legacy names
One-click install
npx skills add https://github.com/THRISHAL12345/Project_X --skill tool-rename-deprecation-thrishal12345
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tool-rename-deprecation
Source: https://github.com/THRISHAL12345/Project_X/tree/main/apps/vscode-fork/.github/skills/tool-rename-deprecation
Command: npx skills add https://github.com/THRISHAL12345/Project_X --skill tool-rename-deprecation-thrishal12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken references when built-in tools or tool sets are renamed, so existing prompts, saved configs, and auto-approval settings keep working.

Core Features & Use Cases

  • Legacy Name Preservation: Ensures old toolReferenceName and referenceName values are retained in the proper legacy arrays.
  • Consumer Coverage Checks: Verifies that prompt resolution, tool enablement, and auto-approval logic all still recognize deprecated names.
  • Safe Refactors: Helps reviewers validate tool registration changes without accidentally breaking activation events or stable IDs.
  • Use Case: When a VS Code tool is renamed, use this Skill to confirm the previous name is preserved and all lookup paths still resolve correctly.

Quick Start

Review the tool registration change and confirm the previous tool or tool set name is still present in the matching legacy array.

Frequently Asked Questions about tool-rename-deprecation

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

FAQPage Schema
How do I keep backward compatibility when renaming a VS Code tool reference?▼

To maintain backward compatibility when renaming a VS Code tool reference, you must retain the old toolReferenceName and referenceName values in the proper legacy arrays. This prevents broken references in prompts, saved configs, and auto-approval workflows.

Why does renaming a tool set break auto-approval settings in VS Code?▼

Renaming a tool set breaks auto-approval settings because the resolution logic matches tools by name. Removing the old identifier causes lookup paths to fail, breaking activation events and stable IDs for existing workflows.

What is the best way to refactor tool registration code without breaking activation events?▼

The best way to refactor tool registration code without breaking activation events is to validate that all consumers still recognize deprecated names. You must verify that prompt resolution, tool enablement, and auto-approval logic all retain old identifiers in legacy arrays.

Does TypeScript tool registration support legacy names for renamed tools?▼

Yes, TypeScript tool registration supports legacy names by retaining old identifiers in legacy arrays. You must validate that prompt files, extension-contributed tools, and auto-approval workflows all continue to recognize deprecated names during resolution.

How do I validate that prompt files still resolve deprecated tool names after refactoring?▼

To validate that prompt files resolve deprecated tool names after refactoring, perform consumer coverage checks across the codebase. Verify that prompt resolution, tool enablement, and auto-approval logic all still recognize the old identifiers in the legacy arrays.

Related Skills

Explore More Software Engineering Skills→
aadorianaadorian

tool-rename-deprecation

Preserve renamed tool references in legacy arrays during registration changes.

Community
Advanced
NithwinNithwin

tool-rename-deprecation

Preserve old tool references during TypeScript renames to maintain backward compatibility.

Community
Advanced
colajacquin-ecolajacquin-e

tool-rename-deprecation

Preserve old tool names in legacy arrays for backward compatibility.

Community
Advanced
ZaxbyHubZaxbyHub
437

pr-readiness

Redirect deprecated pr-readiness skill calls to swarm-pr-feedback in OpenCode Swarm configurations.

Official
Basic