What problem does it solve? Event listeners and disposable objects that are never released cause memory leaks where listener counts grow with every operation, degrading editor performance over time. This Skill provides a systematic checklist to find and fix these leaks in VS Code-style TypeScript codebases. ## Core Features & Use Cases - Six-Step Audit Checklist: Covers DOM event listeners, one-time events, repeated method calls, model-tied DisposableStores, resource pools, and test validation. - Pattern Library with Fixes: Each check pairs an anti-pattern with the correct pattern, such as replacing raw addEventListener with addDisposableListener, or using MutableDisposable for listeners registered in repeatedly-called methods. - Real-World Validation: Every rule is backed by a merged VS Code pull request (e.g., PR #280566, #283466) showing the actual leak it fixed. - Use Case: A terminal find widget leaks one listener per search. The audit identifies the repeated-method-call pattern and fixes it by storing the listener in a MutableDisposable so at most one listener exists at a time. ## Quick Start Review this TypeScript file for memory leaks using the memory leak audit checklist and fix any disposable pattern violations you find.
