What problem does it solve? Investigating memory leaks and performance regressions in VS Code requires manually repeating UI workflows while capturing heap snapshots, which is slow, error-prone, and hard to reproduce. This Skill automates launching Code OSS, driving repeatable scenarios with Playwright over CDP, and collecting verifiable memory artifacts. ## Core Features & Use Cases - Automated scenario runners: Checked-in scripts drive multi-turn Chat sessions, session switching, and workbench CSS performance measurement while sampling renderer heap and writing summary.json plus screenshots. - Targeted heap snapshot capture: Take labeled .heapsnapshot files at warmed-up baseline and later iterations instead of snapshotting every sample, then hand off to heap-snapshot-analysis for object and retainer investigation. - Fix-and-verify workflow: Root-cause leaks with git blame and lifecycle tracing, patch product code, rerun the identical scenario, and compare like-for-like memory trends. - Use Case: A user suspects Chat sessions leak memory. Run the chat-memory-smoke runner for 8 iterations with two snapshot labels, verify summary.json, compare snapshots, fix the leaking disposable chain, and rerun to confirm flat memory growth. ## Quick Start Ask the agent to run the Chat memory smoke runner with a few iterations and no heap snapshots to validate the scenario before capturing targeted heap snapshots.