microsoft/tool-rename-deprecation

Garante que referências renomeadas de ferramentas built-in mantenham compatibilidade reversa. Use ao renomear um toolReferenceName, referenceName de um conjunto de ferramentas ou qualquer identificador de ferramenta. Execute em QUALQUER alteração no código de registro de ferramentas. Abrange legacyToolReferenceFullNames para ferramentas e legacyFullNames para conjuntos de ferramentas.

O que é tool-rename-deprecation?

Esta habilidade, disponível para agentes de IA como Claude Code e Cursor, é essencial para desenvolvedores que trabalham com código de registro de ferramentas built-in. Ela garante que, ao renomear identificadores de ferramentas (como `toolReferenceName` ou `referenceName` de um tool set), a compatibilidade reversa seja preservada automaticamente. A habilidade detecta alterações no código de registro e aplica mapeamentos corretos para nomes legados (`legacyToolReferenceFullNames` para ferramentas individuais e `legacyFullNames` para conjuntos). Isso evita que usuários existentes tenham suas referências quebradas durante renomeações, mantendo a funcionalidade contínua. Sua execução é recomendada em qualquer alteração de registro para prevenir problemas de compatibilidade.

Funciona com~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/microsoft/vscode/tree/main/skills/tool-rename-deprecation

Installed? Explore more Programação e Desenvolvimento skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

O que tool-rename-deprecation faz?

Garanta que referências renomeadas de ferramentas built-in mantenham compatibilidade reversa. Use ao renomear um toolReferenceName, referenceName de um conjunto de ferramentas, ou qualquer identificador de ferramenta. Execute em QUALQUER alteração no código de registro de ferramentas. Abrange legacyToolReferenceFullNames para ferramentas e legacyFullNames para conjuntos de ferramentas.

Individual skills in this repo

This repo contains 10 individual skills — each has its own dedicated page.

microsoft/accessibility

Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.

microsoft/agent-sessions-layout

Agents workbench layout — covers the fixed layout structure, grid configuration, part visibility, editor modal, titlebar, sidebar footer, and implementation requirements. Use when implementing features or fixing issues in the Agents workbench layout.

microsoft/author-contributions

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

microsoft/azure-pipelines

Use when validating Azure DevOps pipeline changes for the VS Code build. Covers queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes without waiting for full CI runs.

microsoft/fix-errors

Guidelines for fixing unhandled errors from the VS Code error telemetry dashboard. Use when investigating error-telemetry issues with stack traces, error messages, and hit/user counts. Covers tracing data flow through call stacks, identifying producers of invalid data vs. consumers that crash, enriching error messages for telemetry diagnosis, and avoiding common anti-patterns like silently swallowing errors.

microsoft/hygiene

Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.

microsoft/memory-leak-audit

Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns.

microsoft/sessions

Agents window architecture — covers the agents-first app, layering, folder structure, chat widget, menus, contributions, entry points, and development guidelines. Use when implementing features or fixing issues in the Agents window.

microsoft/update-screenshots

Download screenshot baselines from the latest CI run and commit them. Use when asked to update, accept, or refresh component screenshot baselines from CI, or after the screenshot-test GitHub Action reports differences. This skill should be run as a subagent.

microsoft/validate-ui-scenario

Use when reproducing a UI bug or verifying a fix by driving a real VS Code window end to end and capturing evidence. Writes a scenario file, runs it against a dev build or installed Insiders, and produces a captioned video, per-step screenshots, a Playwright trace, and an HTML report to attach to an issue or pull request.

Habilidades Relacionadas