← Browse
windows-shell
C1nderC0ated ★ 0
This Claude Code plugin provides four skills for developing, analyzing, and testing large Windows batch and PowerShell scripts: a core workflow with static analysis and byte-safe editing, embedded PowerShell 5.1 semantics, testing harnesses, and a catalog of 114 measured pitfalls. Two always-on guard hooks prevent silent script corruption by refusing Bash commands with doubled backslashes and PowerShell functions named after aliases.
Install
> /plugin marketplace add C1nderC0ated/windows-shell
> /plugin install windows-shell
What it's made of
4 skills · 3 hooks
- Commands
- 0
- Agents
- 0
- Skills
- 4
- MCP servers
- 0
- Hooks
- 3 · PreToolUse
What it needs & plugs into
- API keys
- none
- Paid services
- none detected
- External tools
cdexceptppythonrsys.exit(0)sys.exit(2)'sys.stderr.write(Blocked by the windows-shell-dev guard: this Bash command holds a doubled backslash. On Windows the Bash tool turns every doubled backslash into one before bash runs, even inside single quotes and quoted heredocs, so a script or patch written into the command changes silently (a Python newline escape becomes a real line break, a Windows path stops matching). Write the script or patch to a file with the Write tool and run the file, or change the file with Edit. In a plain command, write a single backslash where one is meant.)sys.stderr.write(The windows-shell plugin hooks are active in this session. This was the self-check: nothing ran.)try:- Talks to
- nothing external detected
Analyzed . Facts extracted from the plugin's files. Prose generated by claude-haiku-4-5-20251001.
Is this your plugin?
Claim it to keep the card accurate and enter the weekly contest. Requires signing in as the GitHub owner (C1nderC0ated).