What problem does it solve? Investigating memory leaks or performance regressions in VS Code requires manually repeating UI workflows and capturing heap snapshots, which is slow, error-prone, and hard to reproduce. This Skill automates launching Code OSS, driving repeatable scenarios, and collecting verifiable memory artifacts. ## Core Features & Use Cases - Automated scenario runners: Checked-in Playwright-based runners drive multi-turn Chat sessions, session switching, and workbench CSS performance measurement while sampling renderer heap. - Targeted heap snapshot capture: Take labeled .heapsnapshot files at warmed-up baselines and later iterations, with screenshots and a machine-readable summary.json for verification. - Fix-and-verify workflow: Guides root-cause analysis with git history, product-code fixes, and like-for-like rerun comparisons to confirm leaks are resolved. - Use Case: You suspect the Chat view leaks memory across turns. Run the chat memory smoke runner with 8 iterations and two snapshot labels, verify the summary, then hand the snapshots to heap-snapshot-analysis to find retained objects. ## Quick Start Ask the agent to run the bundled Chat memory smoke runner with a few iterations and no heap snapshots to validate the scenario before capturing targeted heap snapshots.
