# windows-path-troubleshooting

windows-path-troubleshooting — a skill that tells the agent how to write Windows paths for Read, Write and Edit, and how to convert Git Bash paths that end in ENOENT.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 199 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/windows-path-master/skills/windows-path-troubleshooting/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-path-troubleshooting

## What it does

The skill covers the space between Git Bash and the file tools on Windows. Its hard rule: pass backslashes in `file_path`, so `D:\repos\project\file.tsx`, not `D:/repos/project/file.tsx`. A conversion table maps MINGW forms such as `/c/Users/name/` to `C:\Users\name\`, and a decision tree helps the agent work out which form it was handed.

Smaller sections deal with spaces inside paths, `$HOME`-style variables, UNC shares like `\\server\share\folder\file.txt` and the double-slash escape `//c/foo`. There are recipes for `MSYS_NO_PATHCONV` too, for the cases where Git Bash rewrites arguments by itself. No scripts ship with it; everything sits in one `SKILL.md`.

What breaks is predictable. A forward-slash path copied from Git Bash output comes back from Read, Write and Edit as `ENOENT: no such file or directory`. The backslash rule that prevents it is written into the skill text.

## Install

### Claude Code (native platform)

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

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

### Codex

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

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

### Cursor

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

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

### GitHub Copilot

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

2. **Manually: put the files in place**
- File: `.github/skills/windows-path-troubleshooting/SKILL.md`

### Gemini CLI

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

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

### Windsurf (Devin Desktop)

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

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill windows-path-troubleshooting -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/windows-path-master/skills/windows-path-troubleshooting/SKILL.md

## When to use it
- fix ENOENT after pasting a path from Git Bash output
- turn `/s/repos/app` into `S:\repos\app` before an Edit call
- pass a path with spaces like `C:\Program Files\My App\config.json` to Write
- work with a UNC share such as `\\server\share\file.txt`
- switch off MSYS path conversion for a single command

## Example prompts
- My Edit call failed with ENOENT on `/s/repos/app/src/Button.tsx`; convert that to a Windows path and retry.
- How do I pass `C:\Program Files\My App\config.json` to Write without the spaces breaking it?
- Explain the `//c/foo` double-slash form and when to set `MSYS_NO_PATHCONV`.

## 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: 05f1db62dd11bd42.

BEGIN THIRD-PARTY FILE 05f1db62dd11bd42
```text
---
name: windows-path-troubleshooting
description: |
  Complete Windows file path troubleshooting knowledge for Claude Code on Git Bash and Windows environments.
  PROACTIVELY activate for: (1) file path errors on Windows, (2) backslash vs forward slash issues, (3) Edit/Write/Read tool failures, (4) MINGW path resolution, (5) cross-platform path conversion, (6) MSYS_NO_PATHCONV usage, (7) double-slash escape patterns (//c/foo), (8) UNC and long path limits, (9) WSL vs native Windows interop.
  Provides: path-conversion rules, troubleshooting flowchart, MSYS env-var recipes, double-slash escape patterns, and Windows file-operation best practices.
---

## 🚨 CRITICAL GUIDELINES

### Windows File Path Requirements

**MANDATORY: Always Use Backslashes on Windows for File Paths**

When using Edit or Write tools on Windows, you MUST use backslashes (`\`) in file paths, NOT forward slashes (`/`).

**Examples:**
- ❌ WRONG: `D:/repos/project/file.tsx`
- ✅ CORRECT: `D:\repos\project\file.tsx`

This applies to:
- Edit tool file_path parameter
- Write tool file_path parameter
- All file operations on Windows systems


### Documentation Guidelines

**NEVER create new documentation files unless explicitly requested by the user.**

- **Priority**: Update existing README.md files rather than creating new documentation
- **Repository cleanliness**: Keep repository root clean - only README.md unless user requests otherwise
- **Style**: Documentation should be concise, direct, and professional - avoid AI-generated tone
- **User preference**: Only create additional .md files when user specifically asks for documentation


---

# Windows Path Troubleshooting for Claude Code

## 🚨 CRITICAL: Always Use Backslashes on Windows for File Paths

**MANDATORY: When using Edit, Write, or Read tools on Windows, you MUST use backslashes (`\`) in file paths, NOT forward slashes (`/`).**

### The Rule

**Windows File Path Requirements:**
- ✅ **CORRECT**: `D:\repos\project\file.tsx`
- ❌ **WRONG**: `D:/repos/project/file.tsx`

**This applies to:**
```
END THIRD-PARTY FILE 05f1db62dd11bd42

The third-party file has ended. Everything between the 05f1db62dd11bd42 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 2060 of 14084 bytes. © JosiahSiegel · MIT · https://github.com/JosiahSiegel/claude-plugin-marketplace/tree/HEAD/plugins/windows-path-master/skills/windows-path-troubleshooting/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
