Lang Powershell
Test and lint PowerShell via Pester/Analyzer.
Skill metadata
| Source | Bundled (installed by default) |
| Path | skills/software-development/lang-powershell |
| Version | 1.0.0 |
| Author | VibeOS |
| License | MIT |
| Platforms | linux, macos, windows |
Reference: full SKILL.md
The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.
PowerShell Language Pack Skill
Drive PowerShell work with the project index and standard CLI recipes.
LSP hint: none (toolchain CLI) (editor-side when applicable). Zero new core tools.
What this language is (beginner)
Язык автоматизации от Microsoft. Силён на Windows и Azure; современный pwsh работает и на Linux/macOS.
Лучше всего для:
- Windows admin / Azure
- кроссплатформенные pwsh-скрипты
- модули *.psd1
- CI на Windows runners
When to Use
Выбирай этот pack, если:
- Windows/Azure автоматизация
- есть *.psd1 / build.ps1 / PSScriptAnalyzerSettings
- пользователь просит PowerShell
Manifests (автодетект репозитория): PSScriptAnalyzerSettings.psd1, *.psd1, build.ps1
Обычно рядом: Часто рядом с C#/.NET или Azure Terraform.
См. также skill choose-language-pack, если цель ещё не ясна.
Сначала можно ранжировать packs: vibeos language recommend "…".
When NOT to use
- только Unix CI без Windows → Bash
- общее приложения → C# / TypeScript / Python
Prerequisites
vibeos pack apply lang-powershell --apply
vibeos pack apply project-intelligence --apply
How to Run
vibeos project index build
pwsh -NoProfile -Command "Invoke-ScriptAnalyzer -Path ."
pwsh -NoProfile -Command "Invoke-Pester"
Quick Reference
| Goal | Command |
|---|---|
| Apply pack | vibeos pack apply lang-powershell --apply |
| Doctor | vibeos language doctor powershell |
| Primary test | Invoke-Pester |
| Choose guide | skill choose-language-pack |
| Recommend | vibeos language recommend "…" |
Procedure
- Если язык ещё не выбран для нового проекта — сначала
choose-language-packилиvibeos language recommend. - Work from the project root that matches pack manifests.
- Index query →
read_file→ edit → path-scoped tests when iterating. - Prefer the package manager / toolchain already locked in the repo.
- Explain non-obvious toolchain choices in plain language for the user.
Pitfalls
- Prefer pwsh when available; Windows PowerShell 5.x differs.
- Never embed secrets in .ps1 committed to git.
- Do not invent core tools; stay on
terminal+read_file+ index CLI.
Verification
vibeos language doctor powershell
vibeos project index status