While CMD works, PowerShell gives you object-oriented control. Many policies are exposed via the GroupPolicy module.
To access the Local Group Policy Editor from the command line, you'll use the following syntax: local group policy editor command line
If you want to open the editor focused on a specific section, you can use the /gpobject parameter (though this is rare for local policy). More commonly, administrators create custom MSC consoles, but for local policy, simply running gpedit.msc is the standard. While CMD works
reg add "HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced" /v Hidden /t REG_DWORD /d 1 /f administrators create custom MSC consoles
Install-WindowsFeature -Name GPMC Import-Module GroupPolicy
Not every policy is a direct registry key. Some policies (especially under Security Settings like Account Policies) require secedit (see Part 5). Always test changes first.