Terminal command reference
227 commands with the flags people actually reach for and a worked example each
⌨️ Commands and flags are typed as-is, so they are never translated — only the explanations follow your language.
Files and directories32
Moving, deleting and finding. Some of these do not ask twice, which is why -i becomes a habit.
Text processing32
These were built to be piped together. Three joined commands are usually shorter than one that does everything.
git45
The confusion is that undo has several shapes — moving where a branch points is not the same as adding a commit that reverses it.
Processes and system36
What is running and what is eating the machine. Identifying it comes before killing it.
Networking28
When a connection fails, these narrow down how far it got — name not resolving, no route, or a blocked port.
Archives14
Bundling and compressing are separate jobs: tar bundles, gzip shrinks, and .tar.gz is both.
Permissions15
Numeric and symbolic modes name the same thing: 755 and u=rwx,go=rx are the same permission.
Packages and runtimes25
The question is always what goes where: inside this project, or on the whole machine.
How to read this
- Square brackets [ ] mark a part you may leave out.
- An ellipsis … means you can list more than one.
- Flags are case-sensitive — in some commands -r and -R do different things.
Questions
Q. Why are the command names not translated?
Because you type them as they are. A translated ls is a name the shell does not know. Flags stay for the same reason — only the explanations follow your language.
Q. The flags differ between macOS and Linux.
They do. macOS ships BSD tools, so some GNU flags are missing — sed -i wants an argument, ps does not take -ef. Where they diverge, the description says which platform it belongs to.
Q. How do I spot the commands that cannot be undone?
Their descriptions say so. rm does not use a trash can, dd overwrites a disk if of= is wrong, and git reset --hard and git clean -fd throw away uncommitted work.