What problem does it solve? Event listeners and disposable objects that are never released cause memory leaks that grow with usage, degrading editor performance over time. This Skill provides a systematic checklist to detect and fix the most common leak patterns 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 includes bad/good TypeScript examples using addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose. - Real-World Validation: Every rule is backed by a merged PR reference (e.g., PR #283466, #290505) showing the actual leak it fixed. - Use Case: A terminal find widget leaks one listener per search. Run the audit to identify the repeated-method-call pattern, replace this._register() with a MutableDisposable, and verify with ensureNoDisposablesAreLeakedInTestSuite(). ## Quick Start Review this file for memory leaks using the memory leak audit checklist and report any listeners or disposables that are not properly cleaned up.
