Git Worktree Manager
microsoft/WindowsAppSDK
Creates and manages Git worktrees with PowerShell scripts so separate issues and Copilot sessions each get an isolated branch, build and test environment.
Guide for setting up the multi-root PowerShell VS Code extension/PSES dev workspace.
Install Interactive Extension Testing
$ npx skills add PowerShell/vscode-powershell --skill interactive-extension-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PowerShell/vscode-powershell interactive-extension-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PowerShell/vscode-powershell.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/interactive-extension-testing .claude/skills/interactive-extension-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "interactive-extension-testing" agent skill from https://github.com/PowerShell/vscode-powershell/tree/main/.github/skills/interactive-extension-testing into .claude/skills/interactive-extension-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interactive-extension-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PowerShell/vscode-powershell/tree/main/.github/skills/interactive-extension-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PowerShell/vscode-powershell --skill interactive-extension-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PowerShell/vscode-powershell interactive-extension-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PowerShell/vscode-powershell.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/interactive-extension-testing .agents/skills/interactive-extension-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "interactive-extension-testing" agent skill from https://github.com/PowerShell/vscode-powershell/tree/main/.github/skills/interactive-extension-testing into .agents/skills/interactive-extension-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interactive-extension-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PowerShell/vscode-powershell --skill interactive-extension-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PowerShell/vscode-powershell interactive-extension-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PowerShell/vscode-powershell.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/interactive-extension-testing .cursor/skills/interactive-extension-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "interactive-extension-testing" agent skill from https://github.com/PowerShell/vscode-powershell/tree/main/.github/skills/interactive-extension-testing into .cursor/skills/interactive-extension-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interactive-extension-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PowerShell/vscode-powershell.git --path .github/skills/interactive-extension-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PowerShell/vscode-powershell --skill interactive-extension-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PowerShell/vscode-powershell interactive-extension-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PowerShell/vscode-powershell.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/interactive-extension-testing .gemini/skills/interactive-extension-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "interactive-extension-testing" agent skill from https://github.com/PowerShell/vscode-powershell/tree/main/.github/skills/interactive-extension-testing into .gemini/skills/interactive-extension-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interactive-extension-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PowerShell/vscode-powershell interactive-extension-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PowerShell/vscode-powershell --skill interactive-extension-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PowerShell/vscode-powershell.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/interactive-extension-testing .github/skills/interactive-extension-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "interactive-extension-testing" agent skill from https://github.com/PowerShell/vscode-powershell/tree/main/.github/skills/interactive-extension-testing into .github/skills/interactive-extension-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interactive-extension-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PowerShell/vscode-powershell --skill interactive-extension-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PowerShell/vscode-powershell interactive-extension-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PowerShell/vscode-powershell.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/interactive-extension-testing .opencode/skills/interactive-extension-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "interactive-extension-testing" agent skill from https://github.com/PowerShell/vscode-powershell/tree/main/.github/skills/interactive-extension-testing into .opencode/skills/interactive-extension-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interactive-extension-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
interactive-extension-testing- GitHub stars
- 1.9k
- Token cost
- ~824 tokens
- SKILL.md length
- 317 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guide for setting up the multi-root PowerShell VS Code extension/PSES dev workspace.
- Works in 5 steps: Build PSES first. In , run the PSES… → Ensure the workspace can resolve the… → Ensure the extension can load the… → …
- Asked to open the dev workspace
- SKILL.md covers Prerequisites, Setup, Verify and Cleanup, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Interactive Extension Testing is an agent skill from PowerShell/vscode-powershell. 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.
Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging. It works with PowerShell and Visual Studio Code. The repository describes itself as: Provides PowerShell language and debugging support for Visual Studio Code. The licence is MIT.
When your agent uses it
- Asked to open the dev workspace
- Interactively test the extension
- Set up PSES for F5 debugging
- Open pwsh-extension-dev workspace
Example prompts
- “/interactive-extension-testing”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Build PSES first. In , run the PSES build task (for example,
- Ensure the workspace can resolve the Server root. The workspace defines
- Ensure the extension can load the runtime PSES module. modules/ is gitignored
- Open the dev workspace
- Launch interactively. In VS Code, use F5 → Launch Extension. The workspace
What it can do on your machine
Read from SKILL.md and the folder at commit 9c59338. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Interactive Extension Testing loads about 824 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 317 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from PowerShell/vscode-powershell at commit 9c59338, republished under its MIT licence (© PowerShell). 317 words, ~824 tokens.
Download SKILL.mdSave it as
.claude/skills/interactive-extension-testing/SKILL.md (or your agent's skills folder).- 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.
Interactive Extension Testing
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).
Prerequisites
- Follow
.github/copilot-instructions.mdfor the repository build dependencies and themodules/symlink model. - Confirm these commands are available:
pwsh,dotnet,code, and the PowerShellInvokeBuildmodule. - Have a PSES checkout that can be used as
<pses-checkout>.
Setup
Build PSES first. In
<pses-checkout>, run the PSES build task (for example,Invoke-Build Build) so<pses-checkout>/module/PowerShellEditorServices/binexists. Without that directory, the extensionBuildtask invscode-powershell.build.ps1assertsExtension requires PSES.Ensure the workspace can resolve the Server root. The workspace defines
Clientas<extension-repo>andServeras../PowerShellEditorServices, so a worktree parent may need a sibling link:sh ln -s <pses-checkout> <extension-repo-parent>/PowerShellEditorServicesEnsure the extension can load the runtime PSES module.
modules/is gitignored and should point at the built PSES module directory:sh ln -s <pses-checkout>/module <extension-repo>/modulesIn a normal sibling clone,
Invoke-Build RestoreEditorServicesinvscode-powershell.build.ps1creates thismoduleslink and builds PSES. In a worktree or fresh checkout, create the sibling link first ifGet-EditorServicesPathcannot resolve../PowerShellEditorServices/PowerShellEditorServices.build.ps1.Open the dev workspace:
sh cd <extension-repo> code pwsh-extension-dev.code-workspaceLaunch interactively. In VS Code, use F5 → Launch Extension. The workspace also defines
Launch Extension - Temp Profile; seepwsh-extension-dev.code-workspacefor the current launch/task wiring.
Verify
cd <extension-repo>
readlink modules
test -d modules/PowerShellEditorServices/binThen confirm F5 starts the extension host and attaches to PSES.
Cleanup
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>/PowerShellEditorServicesHow It Resolves
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.
© PowerShell, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/interactive-extension-testing of PowerShell/vscode-powershell.
Open the folder on GitHubat commit 9c59338
Compare with similar skills
Interactive Extension Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Interactive Extension Testing this skillPowerShell/vscode-powershell | 1.9k | — | ~824 | Automated safety check: Pass | MIT | |
| Git Worktree Managermicrosoft/WindowsAppSDK | 4.7k | — | ~2k | Automated safety check: Pass | MIT | |
| Sentry Issue Fix Looptixl3d/tixl | 5.1k | — | ~2.1k | Automated safety check: Notes | MIT | |
| Tilelang Debug Helpertile-ai/tilelang-ascend | 400 | — | ~1.7k | Automated safety check: Notes | MIT | |
| Trust Test AuthoringjohannesPettersson80/trust-platform | 221 | — | ~939 | Automated safety check: Pass | Apache-2.0 | |
| Vscode MCP Architecturetjx666/vscode-mcp | 106 | — | ~1.5k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Sentry Issue Fix Loop
tixl3d/tixl
Walks through open Sentry issues for the tooll3 project, latest first, proposing a fix for each and committing them one at a time with your review between.
Tilelang Debug Helper
tile-ai/tilelang-ascend
How to add debugging capabilities to TileLang Ascend example operators.
Trust Test Authoring
johannesPettersson80/trust-platform
A skill your agent uses for every trust-platform behavior change, bug fix, refactor, malformed input, runtime safety, VS Code, hardware, docs, or supply-chain task that requires a written…
Vscode MCP Architecture
tjx666/vscode-mcp
VSCode MCP Bridge project architecture — current monorepo layout, IPC/EventDispatcher flow, per-workspace socket discovery, MCP/CLI adapters, tool filtering, and VSCode extension services.
- Official
Try Fix Alternative Approach
dotnet/maui
Attempts one alternative fix for a bug, runs the given test command against it and reports what happened, always differing from existing PR fixes.
More from PowerShell/vscode-powershell
Release
PowerShell/vscode-powershell
Guide for preparing a release of the PowerShell VS Code extension.
Update npm Packages
PowerShell/vscode-powershell
Guide for updating NPM dependencies in vscode-powershell. An agent skill from PowerShell/vscode-powershell.
Related
Works with
Categories
Questions about Interactive Extension Testing
What does Interactive Extension Testing do?
Guide for setting up the multi-root PowerShell VS Code extension/PSES dev workspace. Interactive Extension Testing is an agent skill from PowerShell/vscode-powershell. Guide for setting up the multi-root PowerShell VS Code extension/PSES dev workspace.
When should I use Interactive Extension Testing?
Interactive Extension Testing fits situations like: asked to open the dev workspace; interactively test the extension; set up PSES for F5 debugging; open pwsh-extension-dev workspace.
How do I install Interactive Extension Testing in Claude Code?
Run `npx skills add PowerShell/vscode-powershell --skill interactive-extension-testing -a claude-code`. Or copy the skill folder (.github/skills/interactive-extension-testing in PowerShell/vscode-powershell) into .claude/skills/interactive-extension-testing in your project. Claude Code loads it when a task matches its description.
How do I install Interactive Extension Testing in Codex?
Run `npx skills add PowerShell/vscode-powershell --skill interactive-extension-testing -a codex`. Or copy the skill folder (.github/skills/interactive-extension-testing in PowerShell/vscode-powershell) into .agents/skills/interactive-extension-testing in your project. Codex loads it when a task matches its description.
Can I use Interactive Extension Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PowerShell/vscode-powershell --skill interactive-extension-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/interactive-extension-testing, .gemini/skills/interactive-extension-testing, .github/skills/interactive-extension-testing and .opencode/skills/interactive-extension-testing in your project.
What does Interactive Extension Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Interactive Extension Testing is instructions for the agent only.
Does Interactive Extension Testing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Interactive Extension Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Interactive Extension Testing use?
Interactive Extension Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Interactive Extension Testing use?
About 824 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Interactive Extension Testing?
Skills that share tags, products or a category with Interactive Extension Testing: Git Worktree Manager (microsoft/WindowsAppSDK, 4.7k stars), Sentry Issue Fix Loop (tixl3d/tixl, 5.1k stars), Tilelang Debug Helper (tile-ai/tilelang-ascend, 400 stars) and Trust Test Authoring (johannesPettersson80/trust-platform, 221 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Interactive Extension Testing?
PowerShell (a GitHub organization) maintains it in PowerShell/vscode-powershell, which has 1,912 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on August 21, 2026.
Source: PowerShell/vscode-powershell on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.