A practical Linux command list fits thirteen vetted GNU Coreutils templates — pwd, ls, mkdir, cp, mv, cat, head, tail, wc, sort, uniq, df, and du — onto one searchable page that filters by command, category, syntax, or purpose. Every row carries a unique identifier, a short description, and a single template with angle-bracket placeholders such as <file>, <path>, <source>, <destination>, <directory>, and <sorted-file> that the reader substitutes before running. The list intentionally skips destructive flags, recursive removal, force overwrites, privilege escalation, process termination, permission rewriting, package management, and network changes so a quick copy can never silently destroy data on its own. Reading one row tells you what the command inspects or produces; copying it gives you a single template you can paste into a terminal after replacing every placeholder and confirming the working directory, target paths, and the executable source.
When you search "linux command list" you usually want one of three things: a quick reminder of what a familiar command does, a safe template you can copy without rereading the manual, or a vetted short list you can study before going deeper. The Linux Commands Cheat Sheet is built for exactly that recall-and-copy loop. It opens a row for each command, lets you filter the thirteen entries by category or task such as disk or first lines, and copies exactly one template with no filesystem or shell access on the page itself. The thirteen rows are checked for unique identifiers and command strings, and eight templates are fixed against the GNU manual using POSIX utility documentation as an independent cross-check.
What the Thirteen Commands Cover
The thirteen rows split cleanly into five small groups: location, files and directories, preview, counts and ordering, and disk usage. The grouping helps you choose a command by intent instead of by alphabet, which matters when you only remember the task and not the name. Open the Linux Commands Cheat Sheet and the filter box accepts command name, category, syntax fragment, or purpose phrase, so a query like disk or first lines returns the right row without scrolling.
| Command | Category | Typical purpose |
|---|---|---|
| pwd | Location | Print the working directory path |
| ls | Listing | Show directory contents |
| mkdir | Files and directories | Create one directory, with -p for missing parents |
| cp | Files and directories | Copy a source to a destination, prompting before clobber |
| mv | Files and directories | Move or rename a source to a destination, prompting before clobber |
| cat | Text preview | Write file contents to standard output |
| head | Text preview | Show the first twenty lines |
| tail | Text preview | Show the last twenty lines |
| wc | Counts | Count newlines, words, and bytes with -l for lines |
| sort | Ordering | Sort lines according to the active locale |
| uniq | Ordering | Count or strip adjacent duplicates from a sorted file |
| df | Disk usage | Summarize mounted file systems with human-readable units |
| du | Disk usage | Estimate total disk blocks used by a selected path |
Every command above is part of GNU Coreutils and is documented in the GNU Coreutils manual. The cheat sheet's category labels match the same split, so what you read in the manual applies directly to what the template prints.
How to Find and Copy a Template
- Search by command, category, or task such as disk or first lines in the filter box. The thirteen rows narrow to the ones that match your intent, and you do not need to know the exact command name.
- Read the row's description and locate every angle-bracket placeholder in the template. The placeholders are <file>, <path>, <source>, <destination>, <directory>, and <sorted-file>; replace each one with a real value and remove the angle brackets.
- Confirm the working directory, target paths, the executable source, and the local manual before running. Inspect pwd output, resolve any symbolic link, and run command --help or man command on the actual binary your shell will invoke.
- Copy and run only with the permissions you actually need, then verify the observed result and the exit status. A correct command returning a non-zero status still means something failed, so check echo $? right after the command or use set -e in scripts.
These four steps are the entire workflow. The page never opens a terminal, reads a filesystem, executes a command, expands a placeholder, or uploads repository data; copying text is the only side effect, which is what lets you rehearse the steps offline before touching a real machine.
Why Destructive Flags Are Intentionally Missing
A quick-copy reference earns its keep by staying conservative. Context-free destructive commands can discard data and do not belong in a list you copy at a glance, because the reader has not yet confirmed the working directory, resolved symbolic links, or inspected what the path actually points to. Recursive deletion, force overwrites, privilege escalation through sudo, killing processes by pattern, rewriting permissions, package management, and network changes all carry irreversible or hard-to-reverse consequences. The cheat sheet keeps them out on purpose so the act of copying a row cannot, by itself, harm the system.
The copy and move templates still include -i so GNU implementations prompt before overwriting an existing destination. That flag is a guardrail, not a transaction or backup, because interactive prompts can be skipped by aliases, by noninteractive sessions, by scripts that pipe yes into the prompt, and by non-GNU implementations. Treat -i as a friendly second chance rather than a guarantee, and back up important data before any mutation regardless of how safe the template looks.
Reading a Template Safely
Every placeholder hides a real risk if you copy it literally. The angle brackets are not part of the shell syntax, so a template like cp -i <source> <destination> will fail or act on the wrong token if you paste it without editing. Replace the whole placeholder including the brackets, and quote shell-sensitive paths when they contain spaces, metacharacters, or leading hyphens. For filenames that start with a hyphen, use -- before the path when the utility supports it; this stops the leading dash from being parsed as an option. Inspect the working directory with pwd before any command that writes or moves data, because a syntactically valid command can still target the wrong file when the shell expanded wildcards or a relative path differently than you assumed.
Shell metacharacters, whitespace, leading hyphens, wildcard expansion, environment variables, and symbolic links all change what a command targets, so the safest habit is to resolve the path once, copy the resolved absolute path, and paste that absolute value into the placeholder. That single habit removes most of the silent-target surprises that turn a quick command into a recovery job. mkdir -p creates missing parent directories and normally does not complain when the directory already exists, yet it cannot guarantee ownership, permissions, mount availability, or that another process did not replace a path between inspection and use, so even a "safe" mkdir deserves a quick eye on the target before you press enter.
Disk Commands That Disagree on Purpose
The two disk commands measure different things, and a clean Linux command list should make that explicit. df -h summarizes space for mounted file systems using human-readable units, which is the right answer when you want to see which volume is full. du -sh estimates the total blocks attributed to a selected path, which is the right answer when you want to see which folder inside a volume is large. Their totals can differ because deleted-open files, sparse files, hard links, permissions, mount boundaries, snapshots, reserved blocks, and per-file-system accounting affect what each command sees.
Neither command alone proves that a cleanup is safe. When disk pressure is urgent, identify the exact consumer, preserve recoverability, and only then delete anything. The cheat sheet's disk rows give you a quick way to start that investigation without burning the answer into a script before you know what the numbers actually represent.
Counting and Ordering Scopes You Can Trust
Text utilities have precise scopes and the templates respect them. cat writes file contents to standard output and can flood a terminal with large or binary input, so a quick page through the file should use head or tail first; the cheat sheet's head and tail templates show twenty lines, but line delimiters and encodings still matter and the page numbers do not change the byte count of a binary blob.
wc -l counts newline characters rather than a human definition of records, so a file that ends without a trailing newline reports one fewer line than wc sees. sort follows the active locale unless configured otherwise, which can change how accented characters and punctuation are ordered. uniq counts only adjacent duplicates, which is why the placeholder for that row is explicitly named <sorted-file>: feed it unsorted input and it silently returns nothing useful. Preserve original data and review a sample before redirecting transformed output over an important file.
GNU, BSD, BusyBox, and macOS
This cheat sheet targets GNU Coreutils concepts, and options and output can differ on BSD and macOS, on BusyBox environments, inside containers, on minimal images, and on older distributions. The same ls flag, for example, may behave differently or not exist at all. After verifying the executable source with command -v or type, consult the local man page and the binary's --help output before relying on a row on a non-GNU host. The Linux Commands Cheat Sheet is a learning and recall aid, not authorization to operate an unfamiliar server, and the safest next step after copying a template is to confirm the man page matches your platform.
In scripts, handle exit status, quote variables, set an explicit working directory with cd, and choose idempotent operations so reruns do not produce surprising states. Use the least privilege needed and avoid pasting secrets into commands, shell history, filenames, or screenshots. Back up material data before mutations and verify the result afterward. With those habits in place, the thirteen templates on the page become a reliable starting point for the most common shell tasks rather than a shortcut around them.
Related reading: How to Use a Public NTP Server List for Time Setup.
Related reading: Is a PX to REM Converter Safe to Use Online? Privacy.