메뉴
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에 표시된 보조 파일을 읽어 보세요.
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.
SOC 직업 분류 기준
| 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.