$ loading_
自动启动并操控 VS Code Insiders 与 Copilot Chat，完成界面测试、聊天交互和截图。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "launch" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/vscode/main/extensions/copilot/.agents/skills/launch/SKILL.md 2. 保存为 ~/.claude/skills/launch/SKILL.md 3. 装好后重载技能，告诉我可以用了
请启动 VS Code Insiders，并通过 Copilot Chat 执行一轮界面自动化测试：打开聊天面板，发送一条测试消息，验证回复区域是否正常渲染，并输出测试结果摘要。
启动后的自动化测试流程、聊天面板交互结果，以及是否通过的测试摘要。
请启动带调试能力的 VS Code Insiders，打开 Copilot Chat 面板，切换到指定视图，并为当前界面拍摄一张清晰截图保存。
完成指定界面操作，并产出可用于文档或汇报的截图文件。
请自动启动 VS Code Insiders，进入 Copilot Chat 扩展界面，按步骤复现我描述的问题：打开聊天、输入提示词、观察按钮状态变化，并记录异常现象。
问题复现过程记录、关键界面状态变化，以及可用于排查的异常说明。
Automate VS Code Insiders with the Copilot Chat extension using @playwright/cli. VS Code is built on Electron/Chromium and exposes a Chrome DevTools Protocol (CDP) port that @playwright/cli can attach to, enabling the same snapshot-interact workflow used for web pages.
@playwright/cli is available via devDependencies. Run npm install at the repo root, then use npx @playwright/cli to invoke commands. Alternatively, install globally with npm install -g @playwright/cli.code-insiders is required. This extension uses 58 proposed VS Code APIs and targets vscode ^1.110.0-20260223. VS Code Stable will not activate it — you must use VS Code Insiders.npm run compile for a one-shot build, or npm run watch for iterative development..interactive-input-part.monaco-editor.view-line📸 Take screenshots for a paper trail. Use
npx @playwright/cli screenshot --filename=<path>at key moments — after launch, before/after interactions, and when something goes wrong. Screenshots provide visual proof of what the UI looked like and are invaluable for debugging failures or documenting what was accomplished.Save screenshots inside
.vscode-ext-debug/screenshots/(gitignored) using a timestamped subfolder so each run is isolated and nothing gets overwritten:# Create a timestamped folder for this run's screenshots SCREENSHOT_DIR=".vscode-ext-debug/screenshots/$(date +%Y-%m-%dT%H-%M-%S)" mkdir -p "$SCREENSHOT_DIR" # Windows (PowerShell): # $screenshotDir = ".vscode-ext-debug\screenshots\$(Get-Date -Format 'yyyy-MM-ddTHH-mm-ss')" # New-Item -ItemType Directory -Force -Path $screenshotDir # Save a screenshot npx @playwright/cli screenshot --filename="$SCREENSHOT_DIR/after-launch.png"
# Build and launch with the extension
npm run compile
# Use a PERSISTENT user-data-dir so auth state is preserved across sessions.
# .vscode-ext-debug is relative to the project root — works in worktrees and is gitignored.
code-insiders --extensionDevelopmentPath="$PWD" --remote-debugging-port=9223 --user-data-dir="$PWD/.vscode-ext-debug"
# On Windows (PowerShell):
# code-insiders --extensionDevelopmentPath="$PWD" --remote-debugging-port=9223 --user-data-dir="$PWD\.vscode-ext-debug"
# Wait for VS Code to start, retry until attached
for i in 1 2 3 4 5; do npx @playwright/cli attach --cdp=http://127.0.0.1:9223 2>/dev/null && break || sleep 3; done
# Verify you're connected to the right target (not about:blank)
# If `tab-list` shows the wrong target, run `npx @playwright/cli close` and reattach
npx @playwright/cli tab-list
npx @playwright/cli snapshot
# Attach to a specific CDP port
npx @playwright/cli attach --cdp=http://127.0.0.1:9223
After attach, all subsequent commands target the connected app without needing to reattach.
VS Code uses multiple webviews internally. Use tab commands to list and switch between them:
# List all available targets (windows, webviews, etc.)
npx @playwright/cli tab-list
# Switch to a specific tab by index
npx @playwright/cli tab-select 2
…
帮助开发者验证 Azure DevOps 流水线改动，快速排查构建与 YAML 配置问题。
让 AI 通过 Chrome DevTools 控制浏览器并进行调试、自动化与性能分析