launch
Launch Code OSS (VS Code from sources) into an isolated throwaway profile with unique debug ports so you can drive it with @playwright/cli AND attach a Node debugger via dap-cli in the same session. Use when working on VS Code itself and you want to interact with the running workbench, automate chat or UI flows, test UI features, take screenshots, set breakpoints in the renderer / extension host / main process, or combine UI driving with debugging.
Install
git clone https://github.com/microsoft/vscode /tmp/vscode && ln -s /tmp/vscode/.agents/skills/launch ~/.claude/skills/launchFrom README
Code OSS Dev - Launch + Debug You're working on VS Code itself and you want to: Launch a Code OSS build from sources that is already signed in (Copilot, GitHub, etc.) so chat / agent flows work end-to-end. Drive it with @playwright/cli over CDP (UI automation). Optionally attach a debugger via dap-cli to set breakpoints in the renderer, extension host, or main process. Run multiple instances at once without port conflicts. This skill provides a launcher that clones an authenticated user-data-dir to a throwaway temp folder, picks free ports for every debug surface, and prints them as JSON so you can pick them up programmatically. The clone is slim: workspace storage, browser caches, file history, cached VSIX backups, and old logs are excluded by default. On macOS, auth tokens live in the OS keychain plus small files inside User/globalStorage - both of which are preserved.
More from this repo
act-on-feedback
Act on user feedback attached to the current session.
agent-customization
**WORKFLOW SKILL** — Create, update, review, fix, or debug VS Code agent customization files (.instructions.md,...
auto-perf-optimize
Used to run agent-driven VS Code performance or memory investigations.