菜单
Guide for setting up the multi-root PowerShell VS Code extension/PSES dev workspace. Use when asked to open the dev workspace, interactively test the extension, set up PSES for F5 debugging, or open pwsh-extension-dev workspace.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/PowerShell/vscode-powershell --skill interactive-extension-testing命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Guide for preparing a release of the PowerShell VS Code extension. Use when asked to prepare a release, update the version, or create a release PR.
Guide for updating NPM dependencies in vscode-powershell. Use when asked to update packages, fix vulnerabilities, or bump dependency versions.
| name | interactive-extension-testing |
| description | Guide for setting up the multi-root PowerShell VS Code extension/PSES dev workspace. Use when asked to open the dev workspace, interactively test the extension, set up PSES for F5 debugging, or open pwsh-extension-dev workspace. |
Read .github/copilot-instructions.md "Build, Lint, and Test" and "PSES and Cross-Repo Work" first — this skill only adds the worktree setup details for hands-on F5 testing.
Use this when the goal is to open pwsh-extension-dev.code-workspace and run
F5 → Launch Extension against a locally-built PowerShellEditorServices (PSES).
.github/copilot-instructions.md for the repository build dependencies and the
modules/ symlink model.pwsh, dotnet, code, and the PowerShell
InvokeBuild module.<pses-checkout>.Build PSES first. In <pses-checkout>, run the PSES build task (for example,
Invoke-Build Build) so <pses-checkout>/module/PowerShellEditorServices/bin
exists. Without that directory, the extension Build task in
vscode-powershell.build.ps1 asserts Extension requires PSES.
Ensure the workspace can resolve the Server root. The workspace defines
Client as <extension-repo> and Server as ../PowerShellEditorServices, so a
worktree parent may need a sibling link:
ln -s <pses-checkout> <extension-repo-parent>/PowerShellEditorServices
Ensure the extension can load the runtime PSES module. modules/ is gitignored
and should point at the built PSES module directory:
ln -s <pses-checkout>/module <extension-repo>/modules
In a normal sibling clone, Invoke-Build RestoreEditorServices in
vscode-powershell.build.ps1 creates this modules link and builds PSES. In a
worktree or fresh checkout, create the sibling link first if Get-EditorServicesPath
cannot resolve ../PowerShellEditorServices/PowerShellEditorServices.build.ps1.
Open the dev workspace:
cd <extension-repo>
code pwsh-extension-dev.code-workspace
Launch interactively. In VS Code, use F5 → Launch Extension. The workspace
also defines Launch Extension - Temp Profile; see pwsh-extension-dev.code-workspace
for the current launch/task wiring.
cd <extension-repo>
readlink modules
test -d modules/PowerShellEditorServices/bin
Then confirm F5 starts the extension host and attaches to PSES.
Both links are reversible and not under version control: modules is gitignored, and the
sibling PowerShellEditorServices link lives outside <extension-repo>. Cleanup is just:
rm <extension-repo>/modules
rm <extension-repo-parent>/PowerShellEditorServices
Use pwsh-extension-dev.code-workspace as the source of truth for roots and launch
configs. Use Get-EditorServicesPath, RestoreEditorServices, and Build in
vscode-powershell.build.ps1 as the source of truth for how the extension locates,
links, builds, and asserts the local PSES module.