What problem does it solve? Chat UI changes can silently regress rendering performance or introduce memory leaks that only surface after release. This Skill automates benchmarking of the VS Code chat panel against baseline builds and runs memory leak checks, turning subjective performance concerns into statistically validated pass/fail verdicts. ## Core Features & Use Cases - Perf regression testing: Launches VS Code via Playwright Electron, streams mock LLM responses, and compares timing, layout, and rendering metrics against a baseline build using Welch's t-test. - Memory leak detection: Sends sequential messages with forced GC between each, then uses linear regression on heap and DOM node samples to compute per-message growth rates. - Flexible build comparison: Compares local dev builds, production builds, downloaded release versions, or any two commits, with per-build VS Code settings overrides for A/B testing. - Use Case: After modifying chatListRenderer.ts, run the perf regression test with 5 runs against the 1.115.0 release baseline to confirm no statistically significant slowdown before merging. ## Quick Start Run the chat performance regression test comparing my local dev build against the VS Code 1.115.0 baseline with 5 runs and tell me if any metrics regressed.
