auto-perf-optimize

Automate VS Code performance investigations with Playwright CDP and heap profiling.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/THRISHAL12345/Project_X --skill auto-perf-optimize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-perf-optimize
Source: https://github.com/THRISHAL12345/Project_X/tree/main/apps/vscode-fork/.github/skills/auto-perf-optimize
Command: npx skills add https://github.com/THRISHAL12345/Project_X --skill auto-perf-optimize

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/cli, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps investigate whether a VS Code workflow is causing memory growth or performance regressions by automating repeatable scenarios, capturing artifacts, and validating that the scenario actually completed.

Core Features & Use Cases

  • Repeatable scenario automation: Launches Code OSS and drives chat or non-chat workflows with Playwright/CDP so investigations are reproducible.
  • Performance evidence capture: Collects screenshots, summary.json output, renderer heap samples, and targeted heap snapshots for before-and-after comparison.
  • Investigation workflow guidance: Supports smoke runs, profile reuse, scratchpad runners, and handoff to heap-snapshot analysis when object-level inspection is needed.

Quick Start

Run the bundled chat memory smoke runner with a safe scratch workspace and inspect the generated summary and screenshots before deciding whether to capture heap snapshots.

Frequently Asked Questions about auto-perf-optimize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate VS Code performance investigations and memory smoke tests?

Automate VS Code performance investigations by launching Code OSS and driving chat or editor workflows with Playwright CDP. This captures screenshots, summary.json output, and heap samples to validate scenario completion and check for memory growth.

How does heap snapshot collection work for VS Code renderer memory analysis?

Heap snapshot collection targets the VS Code renderer after driving a specific workflow with Playwright CDP. It captures object-level evidence for before-and-after comparison, enabling deeper memory regression analysis when summary validation indicates growth.

Can I use Playwright to drive chat workflows and capture screenshots in Code OSS?

Playwright CDP control supports driving both chat and non-chat workflows in Code OSS. It captures screenshots and summary.json output during the run, providing reproducible performance evidence for memory smoke tests.

Do I need the Code OSS smoke-test driver to run reproducible VS Code performance scenarios?

The Code OSS smoke-test driver support is required to run reproducible VS Code performance scenarios. It works with Playwright CDP and workspace-safe runner configurations using persistent or temporary user-data profiles to ensure valid test cycles.

What is the best way to capture performance evidence for VS Code memory regressions before deep analysis?

Run a bundled memory smoke runner with a safe scratch workspace to capture performance evidence for VS Code memory regressions. Inspect the generated summary and screenshots first, then decide whether targeted heap-snapshot collection is needed for deeper analysis.

Why are my VS Code performance runs not reproducible across different test environments?

VS Code performance runs require workspace-safe runner configuration with persistent or temporary user-data profiles to be reproducible. Using Playwright CDP control with Code OSS ensures consistent launch, drive, capture, and verify cycles across environments.