PowerShell Shell Detection & Compatibility FAQs

Question 1

How does this skill detect PowerShell vs Git Bash?

Accepted Answer

It uses a prioritized detection order, checking for environment variables like PSModulePath for PowerShell and MSYSTEM for Git Bash/MSYS2 to reliably identify the shell context.

Question 2

What is the best way to convert paths between shells?

Accepted Answer

For Git Bash environments, the skill recommends using the 'cygpath' utility to manually convert paths to Unix (-u), Windows (-w), or Mixed (-m) formats for maximum reliability.

Question 3

Why do my file paths break when using Git Bash on Windows?

Accepted Answer

Git Bash often automatically converts Unix-style paths to Windows-style, which can cause issues with command arguments. This skill provides instructions on using MSYS_NO_PATHCONV to control this behavior.

Question 4

Does this support PowerShell 7 and Windows PowerShell 5.1?

Accepted Answer

Yes, the skill includes detection logic that distinguishes between modern PowerShell (Core) 7+ and legacy Windows PowerShell 5.1 using the $PSVersionTable object.

Question 5

Can I use these patterns for CI/CD pipelines?

Accepted Answer

Yes, these detection and compatibility patterns are ideal for writing scripts for GitHub Actions or Azure DevOps where the shell might vary between PowerShell and Bash depending on the runner configuration.

PowerShell Shell Detection & Compatibility

PowerShell Shell Detection & Compatibility

주요 기능

사용 사례

주요 기능

사용 사례