Asegura que las referencias renombradas de herramientas integradas conserven compatibilidad hacia atrás. Se utiliza al renombrar un toolReferenceName, referenceName de un conjunto de herramientas o cualquier identificador de herramienta. Ejecutar en CUALQUIER cambio en el código de registro de herramientas. Cubre legacyToolReferenceFullNames para herramientas y legacyFullNames para conjuntos de herramientas.
Esta habilidad está diseñada para mantener la compatibilidad hacia atrás al renombrar identificadores de herramientas integradas en un sistema de agentes de IA o plataforma de desarrollo. Específicamente, maneja los casos donde se renombra un `toolReferenceName`, `referenceName` de un conjunto de herramientas o cualquier identificador de herramienta. Su objetivo principal es garantizar que las referencias antiguas a estos identificadores (legacyToolReferenceFullNames para herramientas individuales y legacyFullNames para conjuntos de herramientas) sigan funcionando después del cambio, evitando que se rompan integraciones existentes. Se ejecuta ante cualquier modificación en el código de registro de herramientas, proporcionando una capa de seguridad que previene errores de regresión. Es útil para desarrolladores que trabajan con plataformas como Azure AI Agent Service, Copilot Studio, o sistemas similares donde las herramientas tienen identificadores internos que pueden cambiar durante el desarrollo o la refactorización.
npx skills add https://github.com/microsoft/vscode/tree/main/skills/tool-rename-deprecationInstalled? Explore more Programación y desarrollo skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →
Asegura que las referencias renombradas de herramientas integradas conserven compatibilidad hacia atrás. Se utiliza al renombrar un toolReferenceName, referenceName de un conjunto de herramientas o cualquier identificador de herramienta. Se ejecuta en CUALQUIER cambio en el código de registro de herramientas. Cubre legacyToolReferenceFullNames para herramientas y legacyFullNames para conjuntos de herramientas.
This repo contains 10 individual skills — each has its own dedicated page.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Send and manage iMessages via BlueBubbles, including attachments, tapbacks, edits, replies, and groups.
Control Eight Sleep pods (status, temperature, alarms, schedules).
BluOS CLI (blu) for discovery, playback, grouping, and volume.
Create, search, and manage Bear notes via grizzly CLI.
Capture frames or clips from RTSP/ONVIF cameras.
Search GIF providers with CLI/TUI, download results, and extract stills/sheets.