# windows-git-bash-compatibility

windows-git-bash-compatibility fixes path conversion conflicts and shell issues when running Azure Data Factory tooling inside Git Bash on Windows.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 165 installs · ★ 66 repo stars
- Author: JosiahSiegel
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/JosiahSiegel/claude-plugin-marketplace/tree/HEAD/plugins/adf-master/skills/windows-git-bash-compatibility/SKILL.md
- Updated: 2026-06-18
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/windows-git-bash-compatibility

## What it does

Git Bash on Windows translates POSIX path arguments into Windows file paths by default. When running Azure Data Factory commands, this behavior mangles Azure subscription identifiers and factory resource paths passed to CLI tools.

This skill gives your coding agent patterns to disable translation using `MSYS_NO_PATHCONV=1`. It provides safe templates for running `npm run build validate`, exporting ARM templates, and invoking PowerShell deployment scripts directly from bash sessions.

It includes environment detection snippets for Bash and Node.js runtime scripts. Without disabling MSYS path translation, standard calls to `az deployment group create` fail whenever resource IDs begin with a slash.

## Requirements
- Works with: Azure

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill windows-git-bash-compatibility -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/windows-git-bash-compatibility/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/windows-git-bash-compatibility/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill windows-git-bash-compatibility -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/windows-git-bash-compatibility/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill windows-git-bash-compatibility -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/windows-git-bash-compatibility/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install JosiahSiegel/claude-plugin-marketplace plugins/adf-master/skills/windows-git-bash-compatibility
```

2. **Manually: put the files in place**
- File: `.github/skills/windows-git-bash-compatibility/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill windows-git-bash-compatibility -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/JosiahSiegel/claude-plugin-marketplace --path plugins/adf-master/skills/windows-git-bash-compatibility
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/windows-git-bash-compatibility/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill windows-git-bash-compatibility -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/JosiahSiegel/claude-plugin-marketplace/tree/HEAD/plugins/adf-master/skills/windows-git-bash-compatibility/SKILL.md

## When to use it
- prevent path corruption when invoking ADF CLI tools
- pass uncorrupted ARM template paths to Azure CLI
- execute PowerShell deployment scripts from Git Bash
- detect MinGW and Git Bash environments in build scripts

## Example prompts
- Fix the path translation errors when running ADF validation inside Git Bash.
- Show how to pass ARM template parameters to Azure CLI from Windows bash.
- Add Git Bash shell detection to my npm deployment script.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: cb4b70d3919d480c.

BEGIN THIRD-PARTY FILE cb4b70d3919d480c
````text
---
name: windows-git-bash-compatibility
description: |
  Windows and Git Bash compatibility for ADF tooling.
  PROACTIVELY activate for: (1) MSYS_NO_PATHCONV usage with ADF CLI tools, (2) Git Bash path conversion when running ADF npm builds, (3) PowerShell scripts called from Git Bash for ADF, (4) Azure CLI from Git Bash on Windows for ADF deployments, (5) ARM template export issues on Windows, (6) ADF utilities npm package on Windows, (7) line-ending issues in JSON pipeline definitions.
  Provides: MSYS env-var recipes, npm-on-Windows fixes, PowerShell-from-bash patterns, and Azure CLI auth on Git Bash.
---

# Windows & Git Bash Compatibility for Azure Data Factory

## Overview

Azure Data Factory development frequently occurs on Windows machines using Git Bash (MINGW64) as the primary shell. This introduces path conversion challenges that can break CI/CD pipelines, npm commands, and deployment scripts.

## Git Bash Path Conversion Behavior

### Automatic Path Conversion

Git Bash (MINGW) automatically converts Unix-style paths to Windows paths:

**Conversions:**
- `/foo` → `C:/Program Files/Git/usr/foo`
- `/foo:/bar` → `C:\msys64\foo;C:\msys64\bar` (path lists)
- `--dir=/foo` → `--dir=C:/msys64/foo` (arguments)

**What Triggers Conversion:**
- Leading forward slash (`/`) in arguments
- Colon-separated path lists
- Arguments after `-` or `,` with path components

**What's Exempt:**
- Arguments containing `=` (variable assignments)
- Drive specifiers (`C:`)
- Arguments with `;` (already Windows format)
- Arguments starting with `//` (Windows switches)

## ADF-Specific Path Issues

### npm Build Commands

**Problem:**
```bash
# This fails in Git Bash due to path conversion
npm run build validate ./adf-resources /subscriptions/abc/resourceGroups/rg/providers/Microsoft.DataFactory/factories/myFactory

# Path gets converted incorrectly
```

**Solution:**
```bash
# Disable path conversion before running
export MSYS_NO_PATHCONV=1
npm run build validate ./adf-resources /subscriptions/abc/resourceGroups/rg/providers/Microsoft.DataFactory/factories/myFactory

# Or wrap the command
MSYS_NO_PATHCONV=1 npm run build export ./adf-resources /subscriptions/.../myFactory "ARMTemplate"
```

### PowerShell Scripts

**Problem:**
```bash
# Calling PowerShell scripts from Git Bash
pwsh ./PrePostDeploymentScript.Ver2.ps1 -armTemplate "./ARMTemplate/ARMTemplateForFactory.json"
````
END THIRD-PARTY FILE cb4b70d3919d480c

The third-party file has ended. Everything between the cb4b70d3919d480c tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2403 of 12405 bytes. © JosiahSiegel · MIT · https://github.com/JosiahSiegel/claude-plugin-marketplace/tree/HEAD/plugins/adf-master/skills/windows-git-bash-compatibility/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
