Example usage of Get-Command.
Get-Command Get-ChildItemGet-Command is documented in the Microsoft.PowerShell.Core module. Consult the linked reference for syntax and parameters.
Get-Command [[-Name] <string[]>] [-Module <string[]>]This is a practical syntax summary, not every parameter set. Run Get-Command Get-Command -Syntax and Get-Help Get-Command -Full in the installed version for its complete syntax and parameter metadata. Common parameters and -WhatIf/-Confirm support depend on the command and PowerShell version.
Example usage of Get-Command.
Get-Command Get-ChildItemRead all available parameter sets and help for the installed module.
Get-Help Get-Command -Full| Option / clause | Description |
|---|---|
-Name <name[]> | Search command names; supports wildcards. |
-CommandType <type[]> | Limit results to cmdlets, functions, scripts, applications or aliases. |
-Module <name[]> | Search commands exported by selected modules. |
-Syntax | Display syntax for matching commands. |
-ListImported | List commands from imported modules. |
-Verbose | Write additional diagnostic detail to the verbose stream. |
-Debug | Write debugging messages to the debug stream. |
-ErrorAction <action> | Control how a non-terminating error is handled. |
-ErrorVariable <name> | Store error records in a variable. |
-WarningAction <action> | Control how warnings are handled. |
-WarningVariable <name> | Store warning messages in a variable. |
-InformationAction <action> | Control how information messages are handled. |
-InformationVariable <name> | Store information messages in a variable. |
-OutVariable <name> | Store output in a variable as well as sending it onward. |
-OutBuffer <count> | Set the number of objects to collect before the next command runs. |
-PipelineVariable <name> | Store the current pipeline object in a variable during processing. |
-ProgressAction <action> | Control progress reporting in versions that support this parameter. |
-WhatIf / -Confirm | Risk-control parameters available only on commands that support ShouldProcess. |
Review a command and its target before running it. Commands that alter files, services, accounts, disks, permissions or databases may be difficult to reverse. Test in a safe environment and keep backups.