Detect Windows PowerShell 5.1 → 7.x compatibility blockers across a tree of .ps1/.psm1/.psd1 files. Two parts: generate and validate a PSScriptAnalyzer compatibility profile for the target host (the primary detector, covering removed commands/parameters/types), then run a small parser-driven catalog as a sidecar for what PSScriptAnalyzer is structurally blind to — encoding and other behavioral…
Install
npx skills add microsoft/upgrade-agent-plugins --skill scanning-powershell-compatibilitynpx skills add microsoft/upgrade-agent-plugins --skill scanning-powershell-compatibility -a claude-code -gnpx skills add microsoft/upgrade-agent-plugins --skill scanning-powershell-compatibility -a codex -ggemini skills install https://github.com/microsoft/upgrade-agent-plugins.git --path plugins/upgrade-agent/upgrade/dotnet/skills/lazy/pwsh/scanning-powershell-compatibilitygh skill install microsoft/upgrade-agent-plugins scanning-powershell-compatibilitygit clone --depth 1 https://github.com/microsoft/upgrade-agent-plugins /tmp/microsoft__upgrade-agent-plugins
mkdir -p ~/.claude/skills ~/.agents/skills
cp -R /tmp/microsoft__upgrade-agent-plugins/plugins/upgrade-agent/upgrade/dotnet/skills/lazy/pwsh/scanning-powershell-compatibility ~/.claude/skills/scanning-powershell-compatibility # Claude Code
cp -R /tmp/microsoft__upgrade-agent-plugins/plugins/upgrade-agent/upgrade/dotnet/skills/lazy/pwsh/scanning-powershell-compatibility ~/.agents/skills/scanning-powershell-compatibility # Codex, Cursor, Gemini CLI, Copilot, OpenCode