一键导入
shell-conventions
PowerShell shell conventions for Windows. Avoid bash-isms. Reference before running terminal commands.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
PowerShell shell conventions for Windows. Avoid bash-isms. Reference before running terminal commands.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Pull request lifecycle domain knowledge — branch strategy detection, PR size classification, confidence-scored review, git-aware context, PR analytics, dependency management, and split/merge/describe operations.
Production readiness audit domains, weighted scoring criteria, and check specifications for the /preflight workflow.
Application scaffolding orchestrator. Creates full-stack applications from requirements, selects tech stack, coordinates agents.
Production deployment workflows, rollback strategies, and CI/CD best practices.
Internationalization and localization patterns for multi-language applications
Mobile UI/UX patterns for iOS and Android. Touch-first, platform-respectful design with React Native/Expo focus.
| name | shell-conventions |
| description | PowerShell shell conventions for Windows. Avoid bash-isms. Reference before running terminal commands. |
| triggers | ["powershell","terminal","shell","command","run","windows","cli"] |
Environment: Windows PowerShell 5.x (NOT PowerShell 7/Core) Scope: All
run_commandtool calls across all workspaces
&& — It is NOT a valid operator in PowerShell 5.xcd dir && command — Use the Cwd parameter on run_command instead|| as bash-style OR — Use if (-not $?) { ... } instead| Operator | Bash | PowerShell 5.x | Notes |
|---|---|---|---|
&& | Sequential (conditional) | ❌ NOT SUPPORTED | Use ; or Cwd param |
; | Sequential (unconditional) | ✅ Sequential execution | Runs next regardless of exit code |
| | Pipe stdout | ✅ Pipe objects | Different semantics than bash |
|| | OR (run on failure) | ❌ NOT SUPPORTED | Use if (-not $?) { ... } |
> | Redirect stdout | ✅ Redirect output | Same behavior |
2>&1 | Redirect stderr to stdout | ✅ Merge streams | Same behavior |
cd src && npm test && npm run build
# Set Cwd to "src" on run_command, then just run:
npm test
git status; git log --oneline -5
& ".venv\Scripts\ruff.exe" check app/
& ".venv\Scripts\pytest.exe" tests/ -v
| Task | PowerShell Command |
|---|---|
| Run Node.js tests | npm test |
| Run Python tests | & ".venv\Scripts\pytest.exe" tests/ -q |
| Run linter | npm run lint |
| Check git status | git status |
| Build project | npm run build |
| Install deps | npm install |
| List files | Get-ChildItem -Recurse |
| Find in files | Select-String -Pattern "text" -Path "*.md" |
# Activate (PowerShell)
& ".venv\Scripts\Activate.ps1"
# Run without activation (preferred for tool calls)
& ".venv\Scripts\python.exe" -m pytest tests/ -q
& ".venv\Scripts\python.exe" -m ruff check app/
[!TIP] For
run_commandtool calls, prefer calling the executable directly with&rather than activating the virtual environment.