What problem does it solve? Memory leaks from undisposed Disposable objects are hard to trace: leak reports contain transformed stack traces, paired entries, and false positives from reload timing. This Skill provides a systematic workflow to interpret DisposableTracker leak reports, locate the creation point that missed registration, apply the minimal fix, and add regression tests. ## Core Features & Use Cases - Leak report analysis: Decode idx pairs, creation stacks, and report sources to distinguish real leaks from false positives (e.g., reload-path React subscription misreports). - Guided fix patterns: Apply the correct remedy per leak type — _register / DisposableStore.add for service instances, useEffect cleanup for React subscriptions, and synchronous disposal for exit-path resources. - Regression testing: Write cascade-disposal assertions or use the withLeakCheck / useLeakCheck helpers, then verify the test fails without the fix. - Use Case: When the dev console prints "Disposable leak(s) detected" with a stack pointing at lifecycle.ts, use this Skill to trace the owning service, find the creation path missing _register, fix it, and validate with vitest. ## Quick Start Ask the AI to diagnose the Disposable leak report you pasted and fix the missing registration in the owning service.
