Windows Git Bash Paths

What it does

This skill helps AI agents correctly translate file paths when interacting with Windows systems using Git Bash (MINGW/MSYS2). It addresses the issue where Git Bash automatically converts POSIX-style paths to Windows paths, which can cause problems when executing commands or accessing files via tools like SqlPackage and MSBuild. The skill provides guidance on how to avoid these path conversion errors and ensure proper file access within a Windows development environment.

When to use it

• When an AI agent needs to execute command-line tools (like sqlpackage or MSBuild) on a Windows machine using Git Bash.
• When the AI agent is instructed to work with files located in paths that would be interpreted differently by Git Bash and Windows native tools.
• When interacting with SQL Server development environments (SSDT) where path conversions are common.

Key capabilities

• Provides guidance on converting POSIX-style file paths to Windows-style paths using backslashes (\).
• Explains how Git Bash automatically converts paths and the resulting issues.
• Offers best practices for SSDT workflows within a Git Bash environment.
• Emphasizes the importance of using backslashes in file paths when interacting with tools like Edit or Write.

Example prompts

• "Execute SqlPackage to publish MyDB.dacpac."
• "Run MSBuild on the project located at /repos/project."
• "Access and edit the file located at /D/repos/project/file.tsx."

Tips & gotchas

• Crucially, always use backslashes (\) in file paths when using tools like Edit or Write. Forward slashes (/) will cause errors.
• Be aware that Git Bash automatically converts POSIX-style paths to Windows paths, which can lead to unexpected behavior if not handled correctly.
• This skill focuses on path conversion issues within the context of SQL Server development (SSDT) and using Git Bash on Windows.