Context
The PowerShell standard already requires full cmdlet names (never aliases) and Verb-Noun naming with approved verbs.
Gap
The calling-side and parameter-naming conventions are missing:
- When calling a command in shared code, use full parameter names and avoid positional arguments — explicit names survive parameter-set changes and read clearly to someone who does not know the command.
- Name your own parameters to match PowerShell's built-ins (
ComputerName, Path, Name), not ad-hoc names like $Param_Computer or $InstanceName.
Proposed change
Add these to the PowerShell standard's "Shared conventions" (index.md) and/or the Functions.md parameters section, alongside the existing "full cmdlet names, never aliases" rule.
Source
PoshCode — Style Guide "Naming Conventions" and Best Practices TOOL-05; Microsoft PowerShell-Docs style guide, "Using parameters in examples".
Acceptance
The standard requires full parameter names, discourages positional arguments in shared code, and requires standard PowerShell parameter names.
Context
The PowerShell standard already requires full cmdlet names (never aliases) and Verb-Noun naming with approved verbs.
Gap
The calling-side and parameter-naming conventions are missing:
ComputerName,Path,Name), not ad-hoc names like$Param_Computeror$InstanceName.Proposed change
Add these to the PowerShell standard's "Shared conventions" (
index.md) and/or theFunctions.mdparameters section, alongside the existing "full cmdlet names, never aliases" rule.Source
PoshCode — Style Guide "Naming Conventions" and Best Practices TOOL-05; Microsoft PowerShell-Docs style guide, "Using parameters in examples".
Acceptance
The standard requires full parameter names, discourages positional arguments in shared code, and requires standard PowerShell parameter names.