Windows Git Bash Compatibility
CheckedSeamlessly executes Git Bash commands within Windows environments, leveraging JosiahSiegel's compatibility layer for enhanced automation.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add josiahsiegel/claude-plugin-marketplace --skill windows-git-bash-compatibility -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
josiahsiegel
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned josiahsiegel/claude-plugin-marketplace at 5a1b1123b9.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 5a1b1123b9
- Scanned
- 1 file, 436 lines
About this skill
What it does
This skill enables AI agents to execute Git Bash commands within Windows environments, specifically addressing path conversion issues that commonly arise during Azure Data Factory (ADF) development and deployment. It leverages JosiahSiegel's compatibility layer to prevent automatic Unix-style path conversions performed by Git Bash (MINGW64), which can break CI/CD pipelines, npm commands, and other scripts. The skill allows you to temporarily disable this conversion using the MSYS_NO_PATHCONV=1 environment variable.
When to use it
- Running npm build or validation commands in an ADF project where Git Bash path conversions interfere with the process.
- Executing PowerShell scripts from within a Git Bash terminal as part of an automated deployment workflow.
- Troubleshooting CI/CD pipelines that fail due to incorrect path handling by Git Bash.
Key capabilities
- Disables automatic Unix-style path conversion in Git Bash (MINGW64).
- Allows execution of commands with the
MSYS_NO_PATHCONV=1environment variable set. - Specifically addresses issues encountered during Azure Data Factory development and deployment.
Example prompts
- "Run npm build validate ./adf-resources /subscriptions/abc/resourceGroups/rg/providers/Microsoft.DataFactory/factories/myFactory, disabling path conversion."
- "Execute the PowerShell script ./PrePostDeploymentScript.Ver2.ps1 with the ARM template ./ARMTemplate/ARMTemplateForFactory.json, ensuring no path conversions occur."
- “Export MSYS_NO_PATHCONV=1 and then run
npm run build export ./adf-resources /subscriptions/.../myFactory "ARMTemplate"”
Tips & gotchas
- The skill requires a Git Bash (MINGW64) environment to be available.
- Path conversion is disabled only for the specific command executed with the modified environment variable. It doesn't globally disable it within your shell session.
- Be mindful of arguments containing
=(variable assignments), drive specifiers (C:), or those already in Windows format, as these are exempt from conversion.