PowerShell Cmdlet Development Best Practices

Apply these practices when writing, reviewing, or refactoring PowerShell scripts, modules, and advanced functions.

Naming Conventions

PowerShell's discoverability depends on consistent naming. When every command follows the same pattern, users can guess names before they search for them.

Commands

• Use the Verb-Noun format for all functions and cmdlets (e.g., Get-UserProfile, Set-Configuration)
• Use only approved verbs from Get-Verb -- this avoids import warnings and keeps the module discoverable. Common verbs: Get, Set, New, Remove, Invoke, Start, Stop, Export, Import, Test, Update
• Use singular nouns (Get-Process, not Get-Processes) -- even when the command returns multiple objects, the noun describes the type being retrieved
• Use PascalCase for both the verb and noun

Parameters