windows-agent-shell
SolidA 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.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- phuryn
- Repository
- phuryn/product-engineering
- Created
- 2 weeks ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
git-bash-on-windows
Load when an AI coding agent (Claude Code, Hermes, or any other) runs shell commands on Windows through Git Bash or MSYS2, with PowerShell alongside. Triggers: Windows, Git Bash, MSYS, MSYS2, PowerShell, pwsh, path mangling, 'command not found', exit code looks wrong, command fake-succeeded, process won't die, background job died, heredoc broke, backslash disappeared.
windows-agent-automation
Windows-specific traps when an agent or script drives CLIs, schedules jobs, or generates files on Windows — .cmd shims truncating multi-line input, PowerShell 5.1 missing operators, encoding defaults that corrupt output, Task Scheduler instead of cron, and path/credential locations. Use when writing any Python/Node script that shells out on Windows, scheduling a recurring job, debugging "it works when I type it but not from the script", seeing UnicodeEncodeError or garbled characters, or when a subprocess cannot find a command that is clearly on PATH. Every trap here has already cost real hours on this machine.
windows-shell
Write shell commands that actually run on Windows. Use whenever the working machine is Windows and a command, script, path, or setup step is involved, and whenever a command has already failed with "not recognized", "cannot find path", "No such file or directory", a python3 or NUL problem, or CRLF warnings. Covers PowerShell, cmd, Git Bash, WSL, and the traps that differ between them.