CommandFixerWhat CommandFixer does
The short version of what it does and what it knows. It ships its own dictionary rather than asking you to keep one; every correction waits for your approval before it runs.
A built-in dictionary, not one you maintain
It used to ask you to list every typo by hand. It now ships a built-in database of popular CLI tools and their valid subcommands, plus the standard Windows command set, fuzzy-matched against your buffer. There is nothing to configure to get useful corrections.
Fuzzy matching
Your command is compared to known subcommands by string similarity. A near-miss within a configurable threshold becomes a suggestion; anything too far off is left untouched.
Always confirmed
A changed command is never run silently. PSReadLine shows the corrected form and executes only after you accept it with Y or Enter; any other key keeps the line as you typed it.
PS7 and PS5 together
One install hooks both PowerShell 7 (pwsh) and Windows PowerShell 5 (powershell.exe) profiles at once. Uninstall cleanly removes both.
Yours, on your machine
A single Go binary with no CGO and no service. Config and a JSONL corrections log live under your home directory. Nothing leaves your machine.
Real commands left alone
Before it renames a command it asks your PATH. A program that is really installed, such as code, is never rewritten to a near neighbour, even when the database has never heard of it.
No stray >> prompt
A trailing backtick is stripped before the line runs. An unclosed quote or a dangling pipe beeps and stays on the line for you to finish, rather than dropping you into the continuation prompt.
Popular CLI tools and the Windows command set
Subcommands are corrected for these tools out of the
box. Standalone Windows commands (dir, ipconfig,
tasklist and many more) are matched by command name; known
PowerShell aliases are recognised exactly so they are never "corrected". A
line needs two words or more: ipconfg /all is corrected,
ipconfg on its own is left as typed.