448
Since people are curious Ill explain why:
I need to build our project from the remote repo using a PowerShell script (.ps1). I’m using Bash in the VSCode terminal, I have to run the .ps1 script in a new Command Prompt because the compilation takes around 5 minutes and I need my terminal for other things. To do this, the only way is to run a batch file that executes the .ps1 script.
Its an automation so I dont need to touch powershell whatsover and remain in bash terminal. Instead of opening several windows, I automated all so it only takes 1 alias to compile my shit.
The compilation also requires several inputs and "Key Presses", so I automated all of that in the Batch file.
Since you added a question mark, commands is the correct general term. However there are two types that can be a command. Functions: which are written in pure powershell and cmdlets: which are commands provided by dotnet classes. (Also exes and a bunch of other stuff common to other shells can be a command, but that's not important.)
The reason they have different names is early on functions didn't support some of the features available to cmdlets, such as pipeline input. There was later a way to add this support to functions.
In practice call them any of the 3 and people will know that you mean.