auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
Install
Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.
git clone https://github.com/microsoft/vscode /tmp/vscode && ln -s /tmp/vscode/.github/skills/auto-perf-optimize ~/.claude/skills/auto-perf-optimizeFrom README
VS Code Performance Workflow Drive a repeatable VS Code scenario, collect memory/performance artifacts, verify that the scenario actually happened, then hand the resulting heap snapshots to the generic heap-snapshot-analysis skill when object-level investigation is needed. When to Use User describes a VS Code workflow and asks whether it leaks or grows memory User asks the agent to launch VS Code, drive a scenario, and capture heap snapshots User asks to run the Chat memory smoke runner bundled with this skill User wants screenshots, summary.json, renderer heap samples, and targeted .heapsnapshot files for one scenario User wants a new automation runner for a non-Chat VS Code scenario Do not use this skill when snapshots already exist and the user only wants heap object/retainer analysis. Use heap-snapshot-analysis directly. The Story Define the scenario. Write down one warmup action, one repeatable iteration, and one quiescent point where it is fair to force GC and sample memory.