PowerShell环境检测与跨Shell兼容性指南：Windows下区分PowerShell与Git Bash/MSYS2

powershell-shell-detection by josiahsiegel/claude-plugin-marketplace

75 周安装量

21 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/josiahsiegel/claude-plugin-marketplace --skill powershell-shell-detection

开发系统管理命令行工具

🇨🇳中文介绍

PowerShell 环境检测与跨 Shell 兼容性

在 Windows 上区分 PowerShell 与 Git Bash/MSYS2 Shell 的关键指南，包含特定于 Shell 的路径处理方法和兼容性说明。

Shell 检测优先级（Windows）

在 Windows 上工作时，正确识别 Shell 环境对于正确的路径处理和命令执行至关重要。

检测顺序（按可靠性从高到低）

process.env.PSModulePath（PowerShell 特有）
process.env.MSYSTEM（Git Bash/MinGW 特有）
process.env.WSL_DISTRO_NAME（WSL 特有）
uname -s 输出（跨 Shell，需要执行命令）

PowerShell 检测

主要指标

PSModulePath（最可靠）：

# PowerShell detection
if ($env:PSModulePath) {
    Write-Host "Running in PowerShell"
    # PSModulePath contains 3+ paths separated by semicolons
    $env:PSModulePath -split ';'
}

# Check PowerShell version
$PSVersionTable.PSVersion
# Output: 7.5.4 (PowerShell 7) or 5.1.x (Windows PowerShell)

PowerShell 特有变量：

# These only exist in PowerShell
$PSVersionTable    # Version info
$PSScriptRoot      # Script directory
$PSCommandPath     # Script full path
$IsWindows         # Platform detection (PS 7+)
$IsLinux           # Platform detection (PS 7+)
$IsMacOS           # Platform detection (PS 7+)

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

脚本中的 Shell 类型检测

function Get-ShellType {
    if ($PSVersionTable) {
        return "PowerShell $($PSVersionTable.PSVersion)"
    }
    elseif ($env:PSModulePath -and ($env:PSModulePath -split ';').Count -ge 3) {
        return "PowerShell (detected via PSModulePath)"
    }
    else {
        return "Not PowerShell"
    }
}

Get-ShellType

Git Bash / MSYS2 检测

MSYSTEM 环境变量（最可靠）：

# Bash detection in Git Bash/MSYS2
if [ -n "$MSYSTEM" ]; then
    echo "Running in Git Bash/MSYS2: $MSYSTEM"
fi

# MSYSTEM values:
# MINGW64 - Native Windows 64-bit environment
# MINGW32 - Native Windows 32-bit environment
# MSYS    - POSIX-compliant build environment

次要检测方法：

# Using OSTYPE (Bash-specific)
case "$OSTYPE" in
    msys*)   echo "MSYS/Git Bash" ;;
    cygwin*) echo "Cygwin" ;;
    linux*)  echo "Linux" ;;
    darwin*) echo "macOS" ;;
esac

# Using uname (Most portable)
case "$(uname -s)" in
    MINGW64*) echo "Git Bash 64-bit" ;;
    MINGW32*) echo "Git Bash 32-bit" ;;
    MSYS*)    echo "MSYS" ;;
    CYGWIN*)  echo "Cygwin" ;;
    Linux*)   echo "Linux" ;;
    Darwin*)  echo "macOS" ;;
esac

Windows 上的跨 Shell 兼容性

方面	PowerShell	Git Bash/MSYS2
环境变量	`$env:VARIABLE`	`$VARIABLE`
路径分隔符	`;`（分号）	`:`（冒号）
路径风格	`C:\Windows\System32`	`/c/Windows/System32`
主目录	`$env:USERPROFILE`	`$HOME`
临时目录	`$env:TEMP`	`/tmp`
命令格式	`Get-ChildItem`	`ls`（原生命令）
别名	PowerShell cmdlet 别名	Unix 命令别名

路径处理：PowerShell 与 Git Bash

PowerShell 路径处理：

# Native Windows paths work directly
$path = "C:\Users\John\Documents"
Test-Path $path  # True

# Forward slashes also work in PowerShell 7+
$path = "C:/Users/John/Documents"
Test-Path $path  # True

# Use Join-Path for cross-platform compatibility
$configPath = Join-Path -Path $PSScriptRoot -ChildPath "config.json"

# Use [System.IO.Path] for advanced scenarios
$fullPath = [System.IO.Path]::Combine($home, "documents", "file.txt")

Git Bash 路径处理：

# Git Bash uses Unix-style paths
path="/c/Users/John/Documents"
test -d "$path" && echo "Directory exists"

# Automatic path conversion (CAUTION)
# Git Bash converts Unix-style paths to Windows-style
# /c/Users → C:\Users (automatic)
# Arguments starting with / may be converted unexpectedly

# Use cygpath for manual conversion
cygpath -u "C:\path"      # → /c/path (Unix format)
cygpath -w "/c/path"      # → C:\path (Windows format)
cygpath -m "/c/path"      # → C:/path (Mixed format)

Git Bash 中的自动路径转换（关键）

Git Bash/MSYS2 在某些场景下会自动转换路径，这可能导致问题：

触发转换的情况

# Leading forward slash triggers conversion
command /foo         # Converts to C:\msys64\foo

# Path lists with colons
export PATH=/foo:/bar  # Converts to C:\msys64\foo;C:\msys64\bar

# Arguments after dashes
command --path=/foo    # Converts to --path=C:\msys64\foo

免于转换的情况

# Arguments with equals sign (variable assignments)
VAR=/foo command      # NOT converted

# Drive specifiers
command C:/path       # NOT converted

# Arguments with semicolons (already Windows format)
command "C:\foo;D:\bar"  # NOT converted

# Double slashes (Windows switches)
command //e //s       # NOT converted

# Disable ALL conversion (Git Bash)
export MSYS_NO_PATHCONV=1
command /foo  # Stays as /foo

# Exclude specific patterns (MSYS2)
export MSYS2_ARG_CONV_EXCL="*"           # Exclude everything
export MSYS2_ARG_CONV_EXCL="--dir=;/test"  # Specific prefixes

何时在 Windows 上使用 PowerShell 与 Git Bash

使用 PowerShell 的场景：

✅ Windows 特定任务 - 注册表、WMI、Windows 服务
✅ Azure/Microsoft 365 自动化 - Az、Microsoft.Graph 模块
✅ 模块生态系统 - 利用 PSGallery 模块
✅ 面向对象的管道 - 丰富的对象操作
✅ 原生 Windows 集成 - 内置于 Windows
✅ 使用 pwsh 的 CI/CD - GitHub Actions、Azure DevOps
✅ 跨平台脚本编写 - PowerShell 7 可在 Linux/macOS 上运行

PowerShell 示例场景：

# Azure VM management with Az module
Connect-AzAccount
Get-AzVM -ResourceGroupName "Production" |
    Where-Object {$_.PowerState -eq "VM running"} |
    Stop-AzVM -Force

使用 Git Bash 的场景：

✅ Unix 工具兼容性 - sed、awk、grep、find
✅ Git 操作 - 原生 Git 命令行体验
✅ POSIX 脚本执行 - 运行 Linux Shell 脚本
✅ 跨平台 Shell 脚本 - 来自 Linux/macOS 的 Bash 脚本
✅ 文本处理 - Unix 文本实用工具（sed、awk、cut）
✅ 开发工作流 - 配合 Unix 工具的 Node.js、Python、Ruby

Git Bash 示例场景：

# Git workflow with Unix tools
git log --oneline | grep -i "feature" | awk '{print $1}' |
    xargs git show --stat

具备 Shell 感知的脚本设计

检测与适配（PowerShell）

# Detect if running in PowerShell or Git Bash context
function Test-PowerShellContext {
    return ($null -ne $PSVersionTable)
}

# Adapt path handling based on context
function Get-CrossPlatformPath {
    param([string]$Path)

    if (Test-PowerShellContext) {
        # PowerShell: Use Join-Path
        return (Resolve-Path $Path -ErrorAction SilentlyContinue).Path
    }
    else {
        # Non-PowerShell context
        Write-Warning "Not running in PowerShell. Path operations may differ."
        return $Path
    }
}

检测与适配（Bash）

# Detect shell environment
detect_shell() {
    if [ -n "$MSYSTEM" ]; then
        echo "git-bash"
    elif [ -n "$PSModulePath" ]; then
        echo "powershell"
    elif [ -n "$WSL_DISTRO_NAME" ]; then
        echo "wsl"
    else
        echo "unix"
    fi
}

# Adapt path handling
convert_path() {
    local path="$1"
    local shell_type=$(detect_shell)

    case "$shell_type" in
        git-bash)
            # Convert Windows path to Unix style
            echo "$path" | sed 's|\\|/|g' | sed 's|^\([A-Z]\):|/\L\1|'
            ;;
        *)
            echo "$path"
            ;;
    esac
}

# Usage
shell_type=$(detect_shell)
echo "Running in: $shell_type"

变量	PowerShell	Git Bash	用途
用户名	`$env:USERNAME`	`$USER`	当前用户
主目录	`$env:USERPROFILE`	`$HOME`	用户主目录
临时目录	`$env:TEMP`	`/tmp`	临时文件
路径列表	`$env:Path`（`;` 分隔）	`$PATH`（`:` 分隔）	可执行文件路径
Shell 检测	`$env:PSModulePath`	`$MSYSTEM`	Shell 标识符

跨 Shell 变量访问

PowerShell 访问环境变量：

$env:PATH              # Current PATH
$env:PSModulePath      # PowerShell module paths
$env:MSYSTEM           # Would be empty in PowerShell
[Environment]::GetEnvironmentVariable("PATH", "Machine")  # System PATH

Git Bash 访问环境变量：

echo $PATH             # Current PATH
echo $MSYSTEM          # Git Bash: MINGW64, MINGW32, or MSYS
echo $PSModulePath     # Would be empty in pure Bash

示例 1：跨 Shell 文件查找

# Find files modified in last 7 days
Get-ChildItem -Path "C:\Projects" -Recurse -File |
    Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-7) } |
    Select-Object FullName, LastWriteTime

# Same operation in Git Bash
find /c/Projects -type f -mtime -7 -exec ls -lh {} \;

示例 2：进程管理

# Stop all Chrome processes
Get-Process chrome -ErrorAction SilentlyContinue | Stop-Process -Force

# Same operation in Git Bash
ps aux | grep chrome | awk '{print $2}' | xargs kill -9 2>/dev/null

示例 3：文本文件处理

# Extract unique email addresses from logs
Get-Content "logs.txt" |
    Select-String -Pattern '\b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Z|a-z]{2,}\b' |
    ForEach-Object { $_.Matches.Value } |
    Sort-Object -Unique

# Same operation in Git Bash
grep -oE '\b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Z|a-z]{2,}\b' logs.txt |
    sort -u

跨 Shell 问题排查

问题 1：命令未找到

问题： 命令在一个 Shell 中有效，但在另一个中无效

# PowerShell
Get-Process  # Works



# Git Bash
Get-Process  # Command not found

解决方案： 理解 PowerShell cmdlet 在 Bash 中不存在。使用原生命令或在 Git Bash 中安装 PowerShell Core (pwsh)：

# Run PowerShell from Git Bash
pwsh -Command "Get-Process"

问题 2：路径格式不匹配

问题： 路径在不同 Shell 中无效

# Git Bash path
/c/Users/John/file.txt  # Works in Bash

# PowerShell
Test-Path "/c/Users/John/file.txt"  # May fail

解决方案： 使用 cygpath 进行转换或规范化路径：

# Convert to Windows format for PowerShell
win_path=$(cygpath -w "/c/Users/John/file.txt")
pwsh -Command "Test-Path '$win_path'"

问题 3：别名冲突

问题： ls、cd、cat 行为不同

# PowerShell
ls  # Actually runs Get-ChildItem



# Git Bash
ls  # Runs native Unix ls command

解决方案： 在 PowerShell 脚本中使用完整的 cmdlet 名称：

# Instead of: ls
Get-ChildItem  # Explicit cmdlet name

✅ 使用 $PSScriptRoot 处理脚本相对路径
✅ 使用 Join-Path 或 [IO.Path]::Combine() 处理路径
✅ 避免硬编码反斜杠
✅ 使用完整的 cmdlet 名称（无别名）
✅ 在所有目标平台上测试
✅ 使用 $IsWindows、$IsLinux、$IsMacOS 进行平台检测

✅ 检查 $MSYSTEM 以检测 Git Bash
✅ 需要时使用 cygpath 进行路径转换
✅ 设置 MSYS_NO_PATHCONV=1 以禁用自动转换（如需要）
✅ 引用包含空格的路径
✅ 在 Bash 内部使用 Unix 风格路径（/c/...）
✅ 调用 Windows 工具时转换为 Windows 路径

✅ 记录脚本所需的 Shell
✅ 在脚本开始时添加 Shell 检测
✅ 为错误的 Shell 提供清晰的错误消息
✅ 考虑创建包装脚本以实现跨 Shell 兼容性
✅ 如果支持两者，请在 PowerShell 和 Git Bash 中测试

最后更新： 2025年10月

🇺🇸English

PowerShell Shell Detection & Cross-Shell Compatibility

Critical guidance for distinguishing between PowerShell and Git Bash/MSYS2 shells on Windows, with shell-specific path handling and compatibility notes.

Shell Detection Priority (Windows)

When working on Windows, correctly identifying the shell environment is crucial for proper path handling and command execution.

Detection Order (Most Reliable First)

process.env.PSModulePath (PowerShell specific)
process.env.MSYSTEM (Git Bash/MinGW specific)
process.env.WSL_DISTRO_NAME (WSL specific)
uname -s output (Cross-shell, requires execution)

PowerShell Detection

Primary Indicators

PSModulePath (Most Reliable):

# PowerShell detection
if ($env:PSModulePath) {
    Write-Host "Running in PowerShell"
    # PSModulePath contains 3+ paths separated by semicolons
    $env:PSModulePath -split ';'
}

# Check PowerShell version
$PSVersionTable.PSVersion
# Output: 7.5.4 (PowerShell 7) or 5.1.x (Windows PowerShell)

PowerShell-Specific Variables:

# These only exist in PowerShell
$PSVersionTable    # Version info
$PSScriptRoot      # Script directory
$PSCommandPath     # Script full path
$IsWindows         # Platform detection (PS 7+)
$IsLinux           # Platform detection (PS 7+)
$IsMacOS           # Platform detection (PS 7+)

Shell Type Detection in Scripts

function Get-ShellType {
    if ($PSVersionTable) {
        return "PowerShell $($PSVersionTable.PSVersion)"
    }
    elseif ($env:PSModulePath -and ($env:PSModulePath -split ';').Count -ge 3) {
        return "PowerShell (detected via PSModulePath)"
    }
    else {
        return "Not PowerShell"
    }
}

Get-ShellType

Git Bash / MSYS2 Detection

Primary Indicators

MSYSTEM Environment Variable (Most Reliable):

# Bash detection in Git Bash/MSYS2
if [ -n "$MSYSTEM" ]; then
    echo "Running in Git Bash/MSYS2: $MSYSTEM"
fi

# MSYSTEM values:
# MINGW64 - Native Windows 64-bit environment
# MINGW32 - Native Windows 32-bit environment
# MSYS    - POSIX-compliant build environment

Secondary Detection Methods:

# Using OSTYPE (Bash-specific)
case "$OSTYPE" in
    msys*)   echo "MSYS/Git Bash" ;;
    cygwin*) echo "Cygwin" ;;
    linux*)  echo "Linux" ;;
    darwin*) echo "macOS" ;;
esac

# Using uname (Most portable)
case "$(uname -s)" in
    MINGW64*) echo "Git Bash 64-bit" ;;
    MINGW32*) echo "Git Bash 32-bit" ;;
    MSYS*)    echo "MSYS" ;;
    CYGWIN*)  echo "Cygwin" ;;
    Linux*)   echo "Linux" ;;
    Darwin*)  echo "macOS" ;;
esac

Cross-Shell Compatibility on Windows

Critical Differences

Aspect	PowerShell	Git Bash/MSYS2
Environment Variable	`$env:VARIABLE`	`$VARIABLE`
Path Separator	`;` (semicolon)	`:` (colon)
Path Style	`C:\Windows\System32`	`/c/Windows/System32`

Path Handling: PowerShell vs Git Bash

PowerShell Path Handling:

# Native Windows paths work directly
$path = "C:\Users\John\Documents"
Test-Path $path  # True

# Forward slashes also work in PowerShell 7+
$path = "C:/Users/John/Documents"
Test-Path $path  # True

# Use Join-Path for cross-platform compatibility
$configPath = Join-Path -Path $PSScriptRoot -ChildPath "config.json"

# Use [System.IO.Path] for advanced scenarios
$fullPath = [System.IO.Path]::Combine($home, "documents", "file.txt")

Git Bash Path Handling:

# Git Bash uses Unix-style paths
path="/c/Users/John/Documents"
test -d "$path" && echo "Directory exists"

# Automatic path conversion (CAUTION)
# Git Bash converts Unix-style paths to Windows-style
# /c/Users → C:\Users (automatic)
# Arguments starting with / may be converted unexpectedly

# Use cygpath for manual conversion
cygpath -u "C:\path"      # → /c/path (Unix format)
cygpath -w "/c/path"      # → C:\path (Windows format)
cygpath -m "/c/path"      # → C:/path (Mixed format)

Automatic Path Conversion in Git Bash (CRITICAL)

Git Bash/MSYS2 automatically converts paths in certain scenarios, which can cause issues:

What Triggers Conversion

# Leading forward slash triggers conversion
command /foo         # Converts to C:\msys64\foo

# Path lists with colons
export PATH=/foo:/bar  # Converts to C:\msys64\foo;C:\msys64\bar

# Arguments after dashes
command --path=/foo    # Converts to --path=C:\msys64\foo

What's Exempt from Conversion

# Arguments with equals sign (variable assignments)
VAR=/foo command      # NOT converted

# Drive specifiers
command C:/path       # NOT converted

# Arguments with semicolons (already Windows format)
command "C:\foo;D:\bar"  # NOT converted

# Double slashes (Windows switches)
command //e //s       # NOT converted

Disabling Path Conversion

# Disable ALL conversion (Git Bash)
export MSYS_NO_PATHCONV=1
command /foo  # Stays as /foo

# Exclude specific patterns (MSYS2)
export MSYS2_ARG_CONV_EXCL="*"           # Exclude everything
export MSYS2_ARG_CONV_EXCL="--dir=;/test"  # Specific prefixes

When to Use PowerShell vs Git Bash on Windows

Use PowerShell When:

✅ Windows-specific tasks - Registry, WMI, Windows services
✅ Azure/Microsoft 365 automation - Az, Microsoft.Graph modules
✅ Module ecosystem - Leverage PSGallery modules
✅ Object-oriented pipelines - Rich object manipulation
✅ Native Windows integration - Built into Windows
✅ CI/CD with pwsh - GitHub Actions, Azure DevOps
✅ Cross-platform scripting - PowerShell 7 works on Linux/macOS

Example PowerShell Scenario:

# Azure VM management with Az module
Connect-AzAccount
Get-AzVM -ResourceGroupName "Production" |
    Where-Object {$_.PowerState -eq "VM running"} |
    Stop-AzVM -Force

Use Git Bash When:

✅ Unix tool compatibility - sed, awk, grep, find
✅ Git operations - Native Git command-line experience
✅ POSIX script execution - Running Linux shell scripts
✅ Cross-platform shell scripts - Bash scripts from Linux/macOS
✅ Text processing - Unix text utilities (sed, awk, cut)
✅ Development workflows - Node.js, Python, Ruby with Unix tools

Example Git Bash Scenario:

# Git workflow with Unix tools
git log --oneline | grep -i "feature" | awk '{print $1}' |
    xargs git show --stat

Shell-Aware Script Design

Detect and Adapt (PowerShell)

# Detect if running in PowerShell or Git Bash context
function Test-PowerShellContext {
    return ($null -ne $PSVersionTable)
}

# Adapt path handling based on context
function Get-CrossPlatformPath {
    param([string]$Path)

    if (Test-PowerShellContext) {
        # PowerShell: Use Join-Path
        return (Resolve-Path $Path -ErrorAction SilentlyContinue).Path
    }
    else {
        # Non-PowerShell context
        Write-Warning "Not running in PowerShell. Path operations may differ."
        return $Path
    }
}

Detect and Adapt (Bash)

# Detect shell environment
detect_shell() {
    if [ -n "$MSYSTEM" ]; then
        echo "git-bash"
    elif [ -n "$PSModulePath" ]; then
        echo "powershell"
    elif [ -n "$WSL_DISTRO_NAME" ]; then
        echo "wsl"
    else
        echo "unix"
    fi
}

# Adapt path handling
convert_path() {
    local path="$1"
    local shell_type=$(detect_shell)

    case "$shell_type" in
        git-bash)
            # Convert Windows path to Unix style
            echo "$path" | sed 's|\\|/|g' | sed 's|^\([A-Z]\):|/\L\1|'
            ;;
        *)
            echo "$path"
            ;;
    esac
}

# Usage
shell_type=$(detect_shell)
echo "Running in: $shell_type"

Environment Variable Comparison

Common Environment Variables

Variable	PowerShell	Git Bash	Purpose
Username	`$env:USERNAME`	`$USER`	Current user
Home Directory	`$env:USERPROFILE`	`$HOME`	User home
Temp Directory	`$env:TEMP`	`/tmp`

Cross-Shell Variable Access

PowerShell accessing environment variables:

$env:PATH              # Current PATH
$env:PSModulePath      # PowerShell module paths
$env:MSYSTEM           # Would be empty in PowerShell
[Environment]::GetEnvironmentVariable("PATH", "Machine")  # System PATH

Git Bash accessing environment variables:

echo $PATH             # Current PATH
echo $MSYSTEM          # Git Bash: MINGW64, MINGW32, or MSYS
echo $PSModulePath     # Would be empty in pure Bash

Practical Examples

Example 1: Cross-Shell File Finding

PowerShell:

# Find files modified in last 7 days
Get-ChildItem -Path "C:\Projects" -Recurse -File |
    Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-7) } |
    Select-Object FullName, LastWriteTime

Git Bash:

# Same operation in Git Bash
find /c/Projects -type f -mtime -7 -exec ls -lh {} \;

Example 2: Process Management

PowerShell:

# Stop all Chrome processes
Get-Process chrome -ErrorAction SilentlyContinue | Stop-Process -Force

Git Bash:

# Same operation in Git Bash
ps aux | grep chrome | awk '{print $2}' | xargs kill -9 2>/dev/null

Example 3: Text File Processing

PowerShell:

# Extract unique email addresses from logs
Get-Content "logs.txt" |
    Select-String -Pattern '\b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Z|a-z]{2,}\b' |
    ForEach-Object { $_.Matches.Value } |
    Sort-Object -Unique

Git Bash:

# Same operation in Git Bash
grep -oE '\b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Z|a-z]{2,}\b' logs.txt |
    sort -u

Troubleshooting Cross-Shell Issues

Issue 1: Command Not Found

Problem: Command works in one shell but not another

# PowerShell
Get-Process  # Works



# Git Bash
Get-Process  # Command not found

Solution: Understand that PowerShell cmdlets don't exist in Bash. Use native commands or install PowerShell Core (pwsh) in Git Bash:

# Run PowerShell from Git Bash
pwsh -Command "Get-Process"

Issue 2: Path Format Mismatches

Problem: Paths don't work across shells

# Git Bash path
/c/Users/John/file.txt  # Works in Bash

# PowerShell
Test-Path "/c/Users/John/file.txt"  # May fail

Solution: Use cygpath for conversion or normalize paths:

# Convert to Windows format for PowerShell
win_path=$(cygpath -w "/c/Users/John/file.txt")
pwsh -Command "Test-Path '$win_path'"

Issue 3: Alias Conflicts

Problem: ls, cd, cat behave differently

# PowerShell
ls  # Actually runs Get-ChildItem



# Git Bash
ls  # Runs native Unix ls command

Solution: Use full cmdlet names in PowerShell scripts:

# Instead of: ls
Get-ChildItem  # Explicit cmdlet name

Best Practices Summary

PowerShell Scripts

✅ Use $PSScriptRoot for script-relative paths
✅ Use Join-Path or [IO.Path]::Combine() for paths
✅ Avoid hardcoded backslashes
✅ Use full cmdlet names (no aliases)
✅ Test on all target platforms
✅ Use $IsWindows, $IsLinux, $IsMacOS for platform detection

Git Bash Scripts

✅ Check $MSYSTEM for Git Bash detection
✅ Use cygpath for path conversion when needed
✅ Set MSYS_NO_PATHCONV=1 to disable auto-conversion if needed
✅ Quote paths with spaces
✅ Use Unix-style paths (/c/...) within Bash
✅ Convert to Windows paths when calling Windows tools

Cross-Shell Development

✅ Document which shell your script requires
✅ Add shell detection at script start
✅ Provide clear error messages for wrong shell
✅ Consider creating wrapper scripts for cross-shell compatibility
✅ Test in both PowerShell and Git Bash if supporting both

Resources

Last Updated: October 2025

Weekly Installs

Repository

josiahsiegel/cl…ketplace

GitHub Stars

First Seen

Jan 24, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

gemini-cli59

opencode56

claude-code55

codex52

github-copilot48

cursor48

React 组合模式指南：Vercel 组件架构最佳实践，提升代码可维护性

122,000 周安装

PowerShell环境检测与跨Shell兼容性指南：Windows下区分PowerShell与Git Bash/MSYS2

🇨🇳中文介绍

PowerShell 环境检测与跨 Shell 兼容性

Shell 检测优先级（Windows）

检测顺序（按可靠性从高到低）

PowerShell 检测

主要指标

相关 Skills

脚本中的 Shell 类型检测

Git Bash / MSYS2 检测

主要指标

Windows 上的跨 Shell 兼容性

关键差异

路径处理：PowerShell 与 Git Bash

Git Bash 中的自动路径转换（关键）

触发转换的情况

免于转换的情况

禁用路径转换

何时在 Windows 上使用 PowerShell 与 Git Bash

使用 PowerShell 的场景：

使用 Git Bash 的场景：

具备 Shell 感知的脚本设计

检测与适配（PowerShell）

检测与适配（Bash）

环境变量对比

常见环境变量

跨 Shell 变量访问

实用示例

示例 1：跨 Shell 文件查找

示例 2：进程管理

示例 3：文本文件处理

跨 Shell 问题排查

问题 1：命令未找到

问题 2：路径格式不匹配

问题 3：别名冲突

最佳实践总结

PowerShell 脚本

Git Bash 脚本

跨 Shell 开发

资源

🇺🇸English

PowerShell Shell Detection & Cross-Shell Compatibility

Shell Detection Priority (Windows)

Detection Order (Most Reliable First)

PowerShell Detection

Primary Indicators

Shell Type Detection in Scripts

Git Bash / MSYS2 Detection

Primary Indicators

Cross-Shell Compatibility on Windows

Critical Differences

Path Handling: PowerShell vs Git Bash

Automatic Path Conversion in Git Bash (CRITICAL)

What Triggers Conversion

What's Exempt from Conversion

Disabling Path Conversion

When to Use PowerShell vs Git Bash on Windows

Use PowerShell When:

Use Git Bash When:

Shell-Aware Script Design

Detect and Adapt (PowerShell)

Detect and Adapt (Bash)

Environment Variable Comparison

Common Environment Variables

Cross-Shell Variable Access

Practical Examples

Example 1: Cross-Shell File Finding

Example 2: Process Management

Example 3: Text File Processing

Troubleshooting Cross-Shell Issues

Issue 1: Command Not Found

Issue 2: Path Format Mismatches

Issue 3: Alias Conflicts

Best Practices Summary

PowerShell Scripts

Git Bash Scripts

Cross-Shell Development

Resources

最新 Skills