Enforce PowerShell scripting standards with PSScriptAnalyzer and Pester.
npx skills add https://github.com/dragoscirjan/opencode-config --skill lang-ps1
Please help me install this Agent Skill. Skill: lang-ps1 Source: https://github.com/dragoscirjan/opencode-config/tree/main/skills/lang-ps1 Command: npx skills add https://github.com/dragoscirjan/opencode-config --skill lang-ps1
This Skill helps you write PowerShell that is consistent, maintainable, and safer to run by turning scattered scripting habits into a clear set of standards.
Ask the assistant to review or write your PowerShell script according to these standards and to apply clean-code principles alongside lang-ps1.
High-intent search queries and answers about installing and using this skill.
Enforce consistent PowerShell scripting standards by applying approved verbs, CmdletBinding, and ErrorAction Stop to your functions. This ensures your team's automation scripts and modules remain maintainable, readable, and safer to run.
You use PSScriptAnalyzer for linting script style and Pester for running tests in your CI-tested utilities. This combination validates your PowerShell codebase against safe function patterns and reliable tooling practices before deployment.
Writing safe PowerShell module functions requires using CmdletBinding, explicit error handling with ErrorAction Stop, and adding #Requires checks for prerequisites. You must also output objects instead of text to ensure pipeline-friendly design.
Yes, PowerShell automation works better with approved verbs and object-based output because it promotes pipeline-friendly design. This allows your advanced functions to integrate cleanly with other commands in a predictable manner.
The best way to standardize PowerShell codebases for CI-tested utilities is to follow PowerShell Practice and Style guidelines. This turns scattered scripting habits into clear standards for reliable tooling and safe function patterns.
You need #Requires checks in your PowerShell scripts to guarantee prerequisite conditions are met before execution. This reinforces safety and reliability by preventing scripts from running in incompatible environments.
adbertramReview PowerShell code against community best practices and coding standards.
semicolon-devteamExecutes Gradle builds and collects JVM-based project coverage with Surefire/Failsafe reports.
nanorepublicaEnforce standardized test-writing guidelines within Claude Code workflows.
ianyimiEnforce global coding style guidelines across multi-language codebases.
