Linux Command Builder

Pick a task, fill in the values, get a copy-ready command — with an explanation of every flag before you run it.

Forgetting whether it was -maxdepth or -d? Not sure if apt remove keeps the config files? Choose one of the 40+ guided recipes below — files, permissions, processes, packages and system administration — type in your paths and values, and the builder assembles the exact command live. Every flag you switch on gets a plain-English explanation, destructive operations get a red warning before you copy them, and anything you build can be collected into a numbered script you download as a .sh file. Works on Raspberry Pi OS, Debian, Ubuntu and pretty much any other Linux box.

🔒 100% private — nothing is uploaded or stored. Every command is assembled entirely in your browser from the values you type. Your paths, hostnames, usernames and package choices are never sent to a server, logged or saved — so you can safely build commands for machines you would not want to paste into a web form.

1 · Pick a task

2 · Fill in the values

3 · Your command

4 · Your script

Collect commands from any recipes into a numbered script as you go — each one keeps a comment header. Edit freely, then copy or download it as a .sh file to run on your machine.

How a Linux command is put together

Every command line follows the same shape, and once you can read that shape you can read almost any command you find in a guide or on a forum:

sudo find /var/log -name '*.log' -mtime '+7'

Piece	Role
`sudo`	Optional prefix: run the command with root privileges instead of your own.
`find`	The program itself — always first (after sudo).
`/var/log`	A positional argument: what the command acts on. Position matters.
`-name '*.log'`	A flag with a value: changes how the program behaves, plus the data the flag needs.
`-mtime +7'`	Another flag with a value: files modified more than 7 days ago.

Short flags vs long flags

Most GNU tools accept both: -h and --help, -r and --recursive. Long flags are self-documenting; short flags are faster to type.
Short flags can be combined: rm -rf is the same as rm -r -f. Long flags cannot: --recursive --force.
A flag that needs a value takes it after a space (-name pattern) or, for long flags, with an equals sign (--max-depth=2). Flags that are simple on/off switches take no value.
Long flags can often be negated with a --no- prefix: --no-install-recommends.

Where to learn more about any command

man find — the full manual page (press q to quit). Every real command has one.
find --help or find -h — a short flag summary, when the tool supports it.
apropos disk — searches the one-line descriptions of every manual page for a keyword, great for finding tools you didn’t know existed.
Raspberry Pi OS is Debian under the hood, so commands built here behave identically on a Pi, a Debian server or an Ubuntu desktop. Where a command differs between distros (for example package managers: apt vs dnf vs pacman), the recipe says so.

sudo etiquette

sudo applies to one command only, not a whole pipeline: in sudo ls | grep x only ls runs as root. To run the whole line elevated, wrap it: sudo sh -c 'ls | grep x'.
Use sudo only where the recipe needs it — reading files in your home directory doesn’t, and neither does checking disk space.
When a command needs root but you’re not sure it’s safe, run it once with --help first, or read the man page. The warnings this builder shows are the same rules of thumb experienced admins use: think twice before rm -rf, kill -9 and anything that touches /.

Spot a bug or want a custom utility built? I'd love to hear from you. Get in touch
Luke Keam | techgeek.biz