Auditez le code à la recherche de fuites mémoire et de problèmes de gestion des ressources jetables. Utilisez-le lors de la révision des écouteurs d'événements, des gestionnaires DOM, des rappels de cycle de vie ou de la correction de rapports de fuites. Couvre les motifs addDisposableListener, Event.once, MutableDisposable, DisposableStore et onWillDispose.
Cette compétence, `microsoft/memory-leak-audit`, est un outil spécialisé pour les développeurs qui travaillent avec des frameworks basés sur des modèles jetables, comme Visual Studio Code ou d'autres environnements utilisant les bibliothèques `vs/base/common/lifecycle`. Elle automatise la détection de fuites mémoire courantes en analysant le code pour identifier les endroits où des écouteurs d'événements, des gestionnaires DOM, ou des abonnements ne sont pas correctement nettoyés. L'outil se concentre sur les motifs fréquents comme `addDisposableListener`, `Event.once`, `MutableDisposable`, `DisposableStore`, et `onWillDispose`, qui sont souvent sources de fuites s'ils ne sont pas utilisés avec les méthodes de nettoyage appropriées (par exemple, avec `DisposableStore` ou en assignant à `MutableDisposable`). En fournissant des suggestions de corrections spécifiques, cette compétence aide à prévenir les dégradations de performance et les bugs subtils liés à la mémoire, tout en accélérant les révisions de code et les sessions de débogage. Elle est particulièrement utile pour les mainteneurs de projets complexes, les revues de code de grande envergure, ou lors de l'investigation de rapports de fuites mémoire.
npx skills add https://github.com/microsoft/vscode/tree/main/skills/memory-leak-auditInstalled? Explore more Développement et programmation skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →
Auditez le code à la recherche de fuites mémoire et de problèmes de gestion des ressources jetables. Utilisez-le lors de la révision des écouteurs d'événements, des gestionnaires DOM, des rappels de cycle de vie ou de la correction de rapports de fuites. Couvre les motifs addDisposableListener, Event.once, MutableDisposable, DisposableStore et onWillDispose.
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.
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.
Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.
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.