- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add phuryn/product-engineering --skill windows-agent-shell -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add phuryn/product-engineering --skill windows-agent-shell -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add phuryn/product-engineering --skill windows-agent-shell -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add phuryn/product-engineering --skill windows-agent-shell -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/phuryn/product-engineering/tree/HEAD/agent-harness/skills/windows-agent-shellDel publicador
When something works here and breaks there, suspect the environment you did not measure. A Windows coding agent runs through Git Bash, PowerShell or cmd. Each splits arguments, expands characters, converts paths and decodes text differently. A command right in one can pass with a different meaning in another.
Hold the invocation constant before attributing a change to configuration. The shell, CLI version, path spelling and line endings are part of the invocation. Every version-specific line carries its version and observation date. Vendors change these monthly; § Re-verify explains how to retest.
2026-10-24).commandWindows. Apply the guardrail-hooks skill for the hook side.powershell.exe) ships with Windows; PowerShell 7 uses pwsh. A script or instruction saying pwsh fails where it is absent.python <skill dir>/scripts/probe_argv.py <the same arguments>. It prints exactly what the program receives and which encodings its pipes use.\ as an escape. Write C:/Python313/python.exe; Windows accepts it. Backslashes also fed Claude Code's Windows command analyser and caused permission prompts (observed 2026-08-16).C:/work/app rather than c:/work/app with npm --prefix. On Vitest, a lowercase drive can give No test suite found, zero tests and exit 1 (observed 2026-08-22). Keep the command shape constant when comparing runs: changed shapes can look like a worker-count cliff or a broken suite./ into a Windows path before the program sees it. gh api /repos/owner/name fails with invalid API endpoint: "C:/Program Files/Git/repos/owner/name". --flag=/etc/x arrives as --flag=C:/Program Files/Git/etc/x (verified and observed 2026-10-24, Git 2.49.0, gh 2.100.0). Drop the leading slash (gh api repos/owner/name) or set MSYS_NO_PATHCONV=1 for that command./c/x paths before Windows programs open them. Git Bash spells C:/x as /c/x, which Windows programs can't open. Convert paths read from commands (/c/x → C:/x). Claude Code hook-input file paths arrive with backslashes even under Git Bash (docs, read 2026-10-24); normalize before comparing.npm --prefix <worktree> install can create a package junction to another checkout when run from a checkout supplying a package the worktree depends on. Recursive deletion of node_modules, or git worktree remove --force, goes through that junction. Run installs with the target as the process's working directory. List node_modules for junctions before deleting; remove the junction itself first. rmdir on the link doesn't follow it. Then run git worktree remove without --force.git commit -m "..." are command substitution. Backticked words execute and are replaced by their output, usually nothing, without warning. See § Commit messages for the safe spelling.-c.foo=bar token in two. Windows PowerShell 5.1 does this too (reproduced and observed 2026-10-24, 5.1.26100): ["-c", ".a.b=c"] bare, ["-c.a.b=c"] quoted. Quote it, and pin the quoted spelling with a test. A matrix can half-break and look finished: check the assets, not the run. A flag that has never been passed before has never been tested.$LASTEXITCODE, with stderr non-fatal around them. Under $ErrorActionPreference = "Stop", Windows PowerShell 5.1 turns redirected native stderr into a terminating error. Reproduced 2026-10-24 (5.1.26100): an exit-0 program writing one warning, called with 2>&1, ended the script with NativeCommandError.$env:DATABASE_URL = "" removes it, so a loader such as dotenv fills it back in from .env; a supposedly database-free run reaches the configured database. Bash's DATABASE_URL= cmd passes an empty value instead (reproduced and observed 2026-10-25, 5.1.26100). Set a single space when the code trims values to absent, or pass an explicit flag. When an attempt may have touched a real system, say so in the handoff.2026-09-25), which can kill a release between the tag and the installers. Use powershell.exe -NoProfile -ExecutionPolicy Bypass -File <script> from the Bash tool with a long timeout. This has carried 16-minute runs without interruption.Get-Content. It decodes with the ANSI code page. (Get-Content f -Raw) -replace 'a','b' | Set-Content f -Encoding utf8 gives each § a stray Â. It turns every — into â € ”; -Encoding utf8 makes the write look safe, but the damage is on the read. Reproduced and observed 2026-10-24 (5.1.26100): the write also adds a UTF-8 BOM and trailing CRLF.
--body-file or -F body=@file, which reads bytes.check_text.py. Run python <skill dir>/scripts/check_text.py <files> to flag mojibake, BOM, CRLF and invalid UTF-8.git checkout <good-ref> -- <file>. Don't reverse double encoding: CP1252's 0x80–0x9F range doesn't round-trip, so reversal loses characters.cp1250 or cp1252. PYTHONUTF8=1 uses utf-8 (observed 2026-10-24, Python 3.13.1). In piped scripts, reconfigure stdout and stderr to UTF-8 and decode stdin as UTF-8 bytes, or set PYTHONUTF8=1.core.autocrlf can normalize CRLF on commit while leaving the working tree wrong despite .gitattributes specifying eol=lf. Source-anchored tests can fail in a file the batch never touched, misleading a delegate into blaming the checkout.
git ls-files --eol | grep w/crlf. It lists endings differing from the index. Use check_text.py for untracked files; grep -c $'\r' is not reliable under Git Bash.check_text.py --fix-crlf <files>, which changes nothing else.The rule under the cheat sheet: the analyser must never have to infer anything. Every path, directory and write target appears literally in the command. Retest before carrying these workarounds to a newer version.
Auto mode became native Windows' default in 2.1.233; 2.1.232 added a Windows-only static analyser for Git Bash commands. From observed 2026-08-14, ordinary read-only commands stopped for a manual click. The analyser ran after permission decisions and downgraded allow to ask; neither permissions.allow nor an autoMode entry could clear it.
Two upstream issues were closed on 2026-08-20 as fixed in 2.1.233. Its changelog says cd <dir> && <command> > file no longer stops. The 2.1.232 changes for Cygwin-style symlinks and < file were reverted. Measured on 2.1.233, 2026-08-16, chains without a redirect still prompted. This cheat sheet was measured on 2.1.232/2.1.233, 2026-08-16:
Keep independent steps separate and use one command per call. Use ; instead of && when steps are independent. Every extra &&, pipe, glob and quoted regex raised the odds.
Use directory flags for commands resolving configuration from their working directory. Use npm --prefix <dir> run <script>, git -C <dir>, node <absolute script path>, and --cwd <dir> for delegate CLIs. npm --prefix was verified to set the script's own working directory and survive nested npm run. A standalone cd leaving the session's project root was bounced next call with Shell cwd was reset to ... (observed 2026-08-16).
Move loops into scripts without concealing safety-relevant flags from the classifier. A script is fine for moving a loop out of the command. Never use it to hide a safety-relevant flag. It stays on disk and gets read.
Retest the cheat sheet and delete workarounds whose cause is gone. In an auto-mode Windows 11 session on 2.1.310 (observed 2026-10-24), compound commands and heredocs ran without stopping. These included cd <dir> && ls && git log ..., mkdir ... && cd ... && curl -o <file> ..., and heredocs fed to python -. The intervening changelog has heredoc and compound-command fixes in several releases.
Run cd <dir> && sed -n '1,5p' <file> in auto mode on your version. If clean, drop the workaround half: keeping it past its cause uglifies commands for nothing. Keep directory flags, briefs in a file, and dedicated read and search tools regardless; they are correct for other reasons. --cwd keeps a delegate from working in, or resuming a thread from, the wrong repository.
Read auto-mode settings and denial reasons from their effective sources. These facts are not Windows-specific (observed 2026-08-16):
autoMode is read only from user settings, never project .claude/settings*.json. Since 2.1.207, a checked-in repository cannot grant itself rules."$defaults" when extending an autoMode array. Without it, the array replaces the built-in list. For soft_deny, that silently drops force-push and production-deploy protection. claude auto-mode config shows the result./permissions → Recently denied for a classifier block's real reason. Since 2.1.208, the agent sees only Blocked by classifier.Write CLI text to a file and pass it by path. Use git commit -F <file>, gh ... --body-file <file>, or gh api ... -F body=@<file>. The shell expands nothing in the file, and an analyser has nothing to infer.
Use a quoted heredoc where your version accepts it. The usual fix is git commit -F -, never -m "...", because backticks execute and vanish silently (§ Arguments 1). A quoted delimiter (<<'EOF') passes text without expansion. Native Windows auto mode in Claude Code 2.1.232/2.1.233 read heredocs as “expansion obfuscation” and prompted (observed 2026-08-16). On 2.1.310 (observed 2026-10-24), they ran without stopping. Where accepted, git commit -F - <<'EOF' is equally safe.
Never -m with backticks · never text that came through PowerShell 5.1's Get-Content (§ Encoding 1).
When you shell out to someone else's CLI, its version on the target machine is the contract. Local tests and review can pass against tools different from the target's.
gh api user --jq .login, which every plausible version has.{.--json the way the old gh auth status version does.mv -n declines to overwrite; Git Bash's mv exits 0 (observed 2026-09-25).Retest each version-specific fact and replace any line whose behaviour changed. Correct its date too. Delete a workaround whose cause is gone rather than keeping it beside the new fact.
Each rule's origin, the case that taught it, is in receipts.md beside this file; read it when a rule's edge is unclear.
A probe shows the program received the arguments, paths and text you meant. The command means the same thing in the shell that actually runs it.
A coding agent on Windows: Git Bash path rewriting, PowerShell quoting and encoding, CRLF. Use when output comes back garbled, or it works here and breaks there.
---name: windows-agent-shelldescription: A coding agent on Windows: Git Bash path rewriting, PowerShell quoting and encoding, CRLF. Use when output…---# agent-harness/skills/windows-agent-shell/SKILL.mdPreguntas frecuentes
Descarga agent-harness/skills/windows-agent-shell/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/phuryn/product-engineering.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.
becho $?