Community编程与开发github.com

microsoft/工具重命名弃用

确保重命名的内置工具引用保留向后兼容性。在重命名 toolReferenceName、工具集 referenceName 或任何工具标识符时使用。对工具注册代码的任何更改均可运行。涵盖工具的 legacyToolReferenceFullNames 和工具集的 legacyFullNames。

工具重命名弃用 是什么?

此技能旨在防止因重命名内置工具引用而导致的破坏性变更,确保跨版本兼容性。当对工具注册代码进行任何修改时(例如重命名 toolReferenceName、工具集 referenceName 或任何工具标识符),该技能会自动检查并更新遗留引用名称(如工具的 legacyToolReferenceFullNames 和工具集的 legacyFullNames),从而使旧名称在使用时仍能正常工作。这对于维护长期运行的开发者工具链至关重要,尤其是在对内置工具集进行重构或重命名场景下。该技能遵循微软推荐的向后兼容策略,支持在 CI/CD 管道或本地开发环境中集成,适用于 Claude Code、Cursor 或 Codex 等 AI 代理平台,指导开发者在变更工具标识符时自动生成或更新弃用映射条目。

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

Installed? Explore more 编程与开发 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

工具重命名弃用 是做什么的?

确保重命名的内置工具引用保留向后兼容性。在重命名 toolReferenceName、工具集 referenceName 或任何工具标识符时使用。对工具注册代码的任何更改均可运行。涵盖工具的 legacyToolReferenceFullNames 和工具集的 legacyFullNames。

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.

相关技能