Communitygithub.com

microsoft/vscode

用於透過驅動真實的 VS Code 視窗進行端到端測試來重現 UI 錯誤或驗證修復,並擷取相關證據。會撰寫情境檔案並針對開發版或已安裝的 Insiders 版本執行,最終產生附有說明的影片、每步驟螢幕截圖、Playwright 追蹤記錄以及 HTML 報告,以便附加至問題或拉取請求中。

vscode 是什麼?

這項技能稱為「microsoft/vscode」,其主要功能是透過自動化驅動一個真實的 VS Code 視窗來進行端到端 (E2E) 測試,以協助開發者重現 UI 錯誤或驗證修復的正確性。它會根據需求撰寫情境腳本 (Scenario File),並針對開發版本或已安裝的 Insiders 版本執行該腳本。執行完成後,它會自動產生多種證據,包括附有說明的影片、每個操作步驟的螢幕截圖、Playwright 追蹤記錄 (Trace),以及一份 HTML 格式的測試報告。這些產出物可以直接附加在 GitHub Issue 或 Pull Request 中,方便團隊進行錯誤回報或修復驗證。此技能支援 VS Code (包含 Insiders 版本) 與 Playwright 測試框架,非常適合需要高度可信證據的 UI 除錯場景。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add microsoft/vscode

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

vscode 是做什麼的?

用於透過驅動真實的 VS Code 視窗進行端到端測試來重現 UI 錯誤或驗證修復,並擷取相關證據。會撰寫情境檔案並針對開發版或已安裝的 Insiders 版本執行,最終產生附有說明的影片、每步驟螢幕截圖、Playwright 追蹤記錄以及 HTML 報告,以便附加至問題或拉取請求中。

Individual skills in this repo

This repo contains 11 individual skills — each has its own dedicated page.

microsoft/accessibility

Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.

microsoft/agent-sessions-layout

Agents workbench layout — covers the fixed layout structure, grid configuration, part visibility, editor modal, titlebar, sidebar footer, and implementation requirements. Use when implementing features or fixing issues in the Agents workbench layout.

microsoft/author-contributions

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

microsoft/azure-pipelines

Use when validating Azure DevOps pipeline changes for the VS Code build. Covers queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes without waiting for full CI runs.

microsoft/fix-errors

Guidelines for fixing unhandled errors from the VS Code error telemetry dashboard. Use when investigating error-telemetry issues with stack traces, error messages, and hit/user counts. Covers tracing data flow through call stacks, identifying producers of invalid data vs. consumers that crash, enriching error messages for telemetry diagnosis, and avoiding common anti-patterns like silently swallowing errors.

microsoft/hygiene

Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.

microsoft/memory-leak-audit

Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns.

microsoft/sessions

Agents window architecture — covers the agents-first app, layering, folder structure, chat widget, menus, contributions, entry points, and development guidelines. Use when implementing features or fixing issues in the Agents window.

microsoft/tool-rename-deprecation

Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.

microsoft/update-screenshots

Download screenshot baselines from the latest CI run and commit them. Use when asked to update, accept, or refresh component screenshot baselines from CI, or after the screenshot-test GitHub Action reports differences. This skill should be run as a subagent.

microsoft/validate-ui-scenario

Use when reproducing a UI bug or verifying a fix by driving a real VS Code window end to end and capturing evidence. Writes a scenario file, runs it against a dev build or installed Insiders, and produces a captioned video, per-step screenshots, a Playwright trace, and an HTML report to attach to an issue or pull request.

相關技能