linux-terminal-expert
Skill0 starsChanged 23 days agoMITView on GitHub
Use when helping a non-programmer work safely in the Linux terminal and bash, covering navigation, text tools, pipes, scripts, ssh, tmux, cron, archives, processes and Bazzite package commands.
- Pipes a download into a shell
- Reads credentials
- Deletes or force-pushes
- Installs packages
In this repository69 other files it gives its agents.
- ableton-liveSkill
- ableton-push-expertSkill
- ardourSkill
- arduino-electronics-solderingSkill
- audacitySkill
- audio-driver-stacksSkill
- audio-interface-digital-ioSkill
- av-receiver-specialistSkill
- bazzite-kde-linuxSkill
- bitwig-studioSkill
- color-palette-expertSkill
- couch-pc-cec-gaming-modeSkill
- cubaseSkill
- daw-hubSkill
- denon-prime-sc5000-x1800Skill
- design-software-guideSkill
- dj-gig-guideSkill
- dj-specialistSkill
- drawing-tabletsSkill
- dsp-references-and-licencesSkill
- electronic-music-producerSkill
- fl-studioSkill
- fx-plugin-designSkill
- gha-supply-chain-hardeningSkill
- github-for-beginnersSkill
- github-repo-lockdownSkill
- grapheneosSkill
- graphic-design-expertSkill
- hard-dance-productionSkill
- hardstyle-sound-design-notesSkill
- hardware-protocol-captureSkill
- home-network-specialistSkill
- js-to-cpp-dsp-portSkill
- juce-audio-thread-handoffSkill
- juce-expertSkill
- juce-headless-test-snapshotSkill
- knulli-handhelds-m8Skill
- korg-logue-sdk-expertSkill
- linux-audio-productionSkill
- linux-expertSkill
- linux-security-hardeningSkill
- logic-proSkill
- loudness-and-lowend-deliverySkill
- man-page-expertSkill
- max-for-live-expertSkill
- mockup-is-the-pluginSkill
- mockup-to-juce-layoutSkill
- nextcloud-specialistSkill
- photo-editing-color-gradingSkill
- pihole-raspberry-piSkill
- plugin-dsp-qualitySkill
- plugin-fleet-auditSkill
- plugin-performance-profilingSkill
- plugin-security-fuzzingSkill
- plugin-ship-checklistSkill
- pro-toolsSkill
- reaperSkill
- rog-ally-x-bazziteSkill
- sound-engineer-acousticsSkill
- sound-forgeSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. About 0 are common, 9 are distinctive, and 14 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 15
Prefer read-only commands first (ls, cat, less, grep, du, df, ps).
- Distinctive: line 17
Never ask the reader to paste a command they do not understand.
- Very specific: line 18
If an answer is UNVERIFIED, say so and point to explainshell.com or man <cmd>.
- Very specific: line 27
Check the folder with pwd.
- Distinctive: line 46
Delete safely. VERIFIED only that rm is the delete command.
- Very specific: line 49
Prefer KDE Trash from Dolphin, or the trash-cli tool, for things you might want back (UNVERIFIED availability).
- Very specific: line 50
Never run rm -rf with a variable you did not print first.
- Distinctive: line 61
All VERIFIED from tldr pages unless noted.
- Very specific: line 92
Add a folder to PATH in ~/.bashrc: export PATH="$HOME/bin:$PATH" (COMMUNITY), then open a new terminal.
- Distinctive: line 118
Use tmux for long jobs over ssh so a dropped connection does not kill them.
- Distinctive: line 157
Test scripts on a copy of the data first.
- Very specific: line 187
Never kill a process you cannot name.
- Very specific: line 197
Check a download before running it: sha256sum file and compare to the site's published hash.
- Distinctive: line 207
Look for the Flatpak or brew version first.
- Very specific: line 211
Read before running. Paste unknown commands into explainshell.com (VERIFIED: it matches each argument to its help text) or man cmd first.
- Very specific: line 212
Never curl ... | bash or sudo something from a forum without understanding it.
- Very specific: line 215
Use full paths and quotes.
- Very specific: line 217
Use -- before names that start with - (VERIFIED in the Quotes page example cp -- "$src" "$dest").
- Very specific: line 245
Search a project for a word and open the hit: rg -n "word", then less +NUMBER file (UNVERIFIED +N).
- Very specific: line 247
Run a long copy that survives a closed laptop lid or dropped ssh: tmux new -s copy, run rsync inside, Ctrl+B d (VERIFIED).
- Distinctive: line 252
Check spelling and case. Tab-complete it.
- Distinctive: line 255
Not installed? Order: Flatpak, brew, distrobox, then layering (VERIFIED Bazzite docs).
- Very specific: line 262
Only then consider sudo for that single command (VERIFIED tldr sudo).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Linux terminal and shell for a non-programmer
Labels: VERIFIED (source) = read on a fetched page. COMMUNITY = common practice, not read on a page. UNVERIFIED = from memory, check before relying on it. Scope: the shell and command-line workflow only. Man-page reading and general Linux/Bazzite admin live in other skills.
Rules of engagement
- Assume the reader is not a programmer. Plain words first, then one exact step. One change at a time, ask the reader to test, then continue. Explain in plain words first, then give one command, then say what it will do.
- One step at a time. Wait for the output before the next step.
- Prefer read-only commands first (ls, cat, less, grep, du, df, ps). Change things second.
- Preview before any delete or bulk change (see Safe habits).
- Never ask the reader to paste a command they do not understand. Never pipe a download into a shell.
- If an answer is UNVERIFIED, say so and point to explainshell.com or
man <cmd>.
Terminal vs shell vs prompt
- VERIFIED (Greg's Wiki BashGuide): the shell is a command interpreter, "a layer between system function calls and the user". Bash "is not your terminal".
- The terminal is the window (here Konsole). The shell (bash) runs inside it and reads what you type.
- bash is the common default. zsh and fish are other shells. UNVERIFIED: which shell Bazzite KDE gives the reader. Check with
echo $SHELL. - COMMUNITY: fish has friendlier autosuggest but different syntax. Scripts written for bash will not all run in fish. Keep scripts as bash with a shebang.
- Reading a prompt: UNVERIFIED (PS1 page not fetched). Typical shape is
user@host:folder$.~means home.$is a normal user.#means root. - Check the folder with
pwd. Check who you are withwhoami.
Navigation and files
Step 1: look around. VERIFIED (tldr ls, cd):
pwd # where am I
ls -la # long list, hidden files too
ls -lh # human sizes
ls -ltr # oldest first, newest last
cd ~ # home; cd - = previous folder; cd .. = up
mkdir -p a/b/c # make nested foldersCopy and move. VERIFIED (GNU coreutils cp, mv): both overwrite existing files by default.
- cp:
-rcopies folders,-akeeps attributes,-iasks before overwrite,-nnever overwrites,-vshows each file. - mv:
-iasks,-nnever overwrites,-vshows each file. - Habit:
cp -iv src destandmv -iv src dest. - Tab completes names. Quote or backslash names with spaces.
Delete safely. VERIFIED only that rm is the delete command; the GNU rm page failed to load, so flag details are UNVERIFIED.
- rm does not use a trash. COMMUNITY: no undo. UNVERIFIED: GNU rm
-Iprompts once before bulk deletes; checkman rm. - Preview first:
ls <same pattern>, thenrm -v <pattern>. - Prefer KDE Trash from Dolphin, or the
trash-clitool, for things you might want back (UNVERIFIED availability). - Never run
rm -rfwith a variable you did not print first.
Find things.
- VERIFIED (tldr find):
find DIR -name '*.ext',-inamefor any case,-type dfor folders,-maxdepth 1,-size +500k,-not -path '*/x/*'. - VERIFIED:
find ... -empty -delete -printdeletes. Run it WITHOUT-deletefirst. - VERIFIED (tldr locate): locate uses a database that refreshes daily or weekly;
sudo updatedbrebuilds it. Quote the pattern. - VERIFIED (tldr fd):
fd "regex"is a friendlier find if installed. - VERIFIED (Greg's Wiki ParsingLs): do not parse
lsoutput in scripts. Use globs orfind -print0.
Text tools
All VERIFIED from tldr pages unless noted.
less file # q quits, /word searches, n next, G end, g start, F follow
head -n 20 file tail -n 20 file tail -f file # follow a log, Ctrl+C stops
grep -rI "word" DIR # search recursively, skip binaries
grep -n -i "word" file # line numbers (-n), ignore case (-i)
grep -F "a.b" file # literal text, not a pattern
grep -v "word" # lines NOT matching; grep -C 3 = 3 lines of context
rg "word" # ripgrep: recursive by default; -l lists files; -g '*.md' filters
sort file | uniq -c | sort -nr # count repeats, most common first
cut -d ',' -f 1,3 file # columns from a CSV-like file
tr 'a-z' 'A-Z' < file # swap characters; tr -d '\r' removes Windows line ends
wc -l file # count lines
diff -u old new # show changes; diff -rq dirA dirB = which files differ
sed 's/old/new/g' file # replace in output; the file is NOT changed
awk '{print $2}' file # print the second column- uniq only joins neighbours, so sort first (VERIFIED, tldr uniq).
- sed
-iedits the file in place. UNVERIFIED on this machine: always test without-ifirst, orcp file file.bak.
Pipes, redirection, quoting, globs, variables, PATH
- Pipe
|sends one command's output into the next. VERIFIED (tldr usage above); the GNU Pipelines page failed to load. - VERIFIED (GNU Bash manual, Redirections):
>writes a file and truncates it to zero size,>>appends,<reads,2>sends errors,&>sends both,2>&1makes errors follow output. - VERIFIED: order matters.
cmd > f 2>&1sends both to f.cmd 2>&1 > fdoes not. - Danger:
>on an existing file destroys it. Use>>or a new name. - VERIFIED (Greg's Wiki Quotes): double-quote every expansion.
cp -- "$src" "$dest", notcp $src $dest. Single quotes are fully literal. A backslash escapes one character. - VERIFIED (Greg's Wiki glob):
*is any string,?is one character,[abc]one of a set. Dotfiles are not matched by*. A glob with no match stays as literal text unlessnullglobis set. Globs do not split names with spaces. - Variables:
name="value"with no spaces around=; read it as"$name". UNVERIFIED in detail (Shell-Variables page failed). - Environment variable for one command:
LANG=C sort file. Export for children:export NAME=value. COMMUNITY. - PATH is the list of folders searched for commands. See it with
echo "$PATH". UNVERIFIED (GNU page failed). To run a script in the current folder use./script.sh. - Add a folder to PATH in
~/.bashrc:export PATH="$HOME/bin:$PATH"(COMMUNITY), then open a new terminal.
History and shortcuts
- VERIFIED (GNU Bash manual): readline keys: Ctrl+A start of line, Ctrl+E end, Alt+B / Alt+F back or forward a word, Ctrl+L clear screen, Ctrl+K kill to end, Ctrl+U kill to start, Ctrl+W kill word behind, Ctrl+Y paste what you killed.
- UNVERIFIED (page failed): Ctrl+R searches history backward; type part of a command, press Ctrl+R again for older matches.
- VERIFIED (GNU Event Designators):
!!repeats the last command,!stringthe last one starting with string,^old^new^repeats it with a swap. - VERIFIED (tldr sudo, history):
sudo !!repeats the last command with sudo. A leading space keeps a command out of history (shell setting dependent, UNVERIFIED).history 20shows the last 20. - VERIFIED: history is saved in
~/.bash_history(HISTFILE), size set by HISTSIZE (default 500). - Ctrl+C stops a running command. Ctrl+D ends input or logs out. Tab completes.
- Konsole: VERIFIED (KDE UserBase): Shift+Ctrl+T new tab; double-click a tab to rename it. UNVERIFIED: Ctrl+Shift+C / Ctrl+Shift+V copy and paste; split view under View menu; Settings, Edit Current Profile for fonts. Ctrl+C in a terminal stops commands, it does not copy.
Job control, tmux, screen
- VERIFIED (GNU Job Control): Ctrl+Z stops the foreground job;
jobslists;bgcontinues it in the background;fgbrings it back;cmd &starts in the background;%1 &resumes job 1. - VERIFIED (tldr nohup):
nohup cmd > out.log &keeps running after the terminal closes. - tmux: VERIFIED (man7 tmux, tldr tmux). Prefix is Ctrl+B. Press the prefix, release, then a key.
tmux new -s work # start a named session
Ctrl+B then d # detach, it keeps running
tmux ls # list sessions
tmux attach -t work # come back
Ctrl+B then c # new window; " splits top/bottom; % splits left/right
tmux kill-session -t work- screen: VERIFIED (tldr screen):
screen -S name, detachCtrl+A d,screen -ls,screen -r name. - Use tmux for long jobs over ssh so a dropped connection does not kill them. COMMUNITY.
ssh basics
- VERIFIED (man7 ssh):
ssh [user@]host [command];-p PORT;-i keyfile;-vfor debug (up to-vvv);-L local:host:remoteforwards a port. - VERIFIED: first connect shows the server key fingerprint; accepted keys go to
~/.ssh/known_hosts; a changed key triggers a warning. Do not ignore that warning without asking the owner. - VERIFIED: per-user config is
~/.ssh/configand needs strict permissions. Keys are made withssh-keygen; the public key goes in~/.ssh/authorized_keyson the server. - Copy files:
rsync -a --dry-run src/ user@host:dest/first (VERIFIED, tldr rsync mentions--dry-run,-a,user@host:path). Then run without--dry-run. - Trailing slash on rsync source matters. UNVERIFIED here; test with
--dry-run.
sudo and permission errors
- VERIFIED (tldr sudo): sudo runs one command as superuser;
sudo -e fileedits a root file safely;sudo -iopens a root shell (avoid). - "Permission denied": read it, do not just add sudo. Check
ls -l fileandwhoami. - VERIFIED (man7 chmod):
chmodsymbolic form[ugoa][+-=][rwx]; numeric is octal (4 read, 2 write, 1 execute for owner, group, others).-Ris recursive. - VERIFIED (tldr chmod):
chmod u+x script.shmakes your own script runnable.chmod -Ron a wrong folder can break a system, so name the folder fully. - VERIFIED (tldr chown):
sudo chown user:group path. Never runchmod -Rorchown -Ron/,/usr,/etcor all of$HOME. - On Bazzite,
/usris read-only by design. "Read-only file system" there is normal, not a bug. COMMUNITY (see bazzite-kde-linux skill).
Scripts
Step 1: make a file, e.g. ~/bin/backup.sh. UNVERIFIED layout, COMMUNITY style:
#!/usr/bin/env bash
set -euo pipefail
src="$HOME/Music/projects"
dest="$HOME/backup"
mkdir -p "$dest"
for f in "$src"/*.als; do
cp -iv -- "$f" "$dest/"
doneStep 2: chmod u+x ~/bin/backup.sh, then shellcheck ~/bin/backup.sh, then run it.
- Shebang
#!/usr/bin/env bashon line 1 picks the interpreter. COMMUNITY. - VERIFIED (GNU Set Builtin):
-eexits on a failing command,-utreats unset variables as errors,-o pipefailmakes a pipeline fail if any part fails (return value of the last non-zero command). - UNVERIFIED:
set -ehas surprising exceptions (insideif,&&chains). It is a safety net, not a guarantee. - VERIFIED (GNU Looping, Functions):
for x in a b c; do echo "$x"; done. Function:name () { commands; }, and inside it$1is the first argument. - VERIFIED (ShellCheck wiki): ShellCheck is a static analysis tool; run
shellcheck script. SC2086 flags unquoted expansions: use"$1"and"$@", or an array for option lists. - Install: VERIFIED (ShellCheck README):
dnf install ShellCheck,brew install shellcheck. On Bazzite preferbrew install shellcheck(COMMUNITY, see packages). - Test scripts on a copy of the data first.
Scheduling: cron vs systemd timers
- VERIFIED (man7 crontab): five fields: minute 0-59, hour 0-23, day of month 1-31, month 1-12, day of week 0-7 (0 and 7 Sunday). Ranges
8-11, lists1,2,5, steps0-23/2.@reboot,@daily(=0 0 * * *). - VERIFIED: cron sets SHELL to /bin/sh. Output is mailed to the owner unless MAILTO is empty. Edit with
crontab -e(UNVERIFIED: edit command not on the fetched page). - UNVERIFIED: cron's PATH is minimal. Use full paths to commands in cron lines.
- VERIFIED (man7 systemd.timer):
foo.timeractivatesfoo.serviceby default.OnCalendar=is wall-clock time.OnBootSec=is time after boot.Persistent=truecatches up missed runs (OnCalendar only). - COMMUNITY: on Bazzite prefer a user systemd timer (
systemctl --user) so missed runs are caught up and logs go tojournalctl --user. UNVERIFIED on this machine; check cronie is installed before relying on cron.
Archives and compression
- VERIFIED (tldr tar):
tar czf out.tar.gz DIRmakes;tar xf in.tar.gz -C DESTextracts;tar tvf in.tarlists WITHOUT extracting;tar caf out.tar.xz filespicks compression from the name. - VERIFIED (tldr zip, unzip):
zip -r out.zip DIR;unzip -l f.ziplists;unzip f.zip -d DEST. - VERIFIED (tldr gzip, xz): both replace the original unless
-kis given. - Habit: list (
tar tvf,unzip -l) before extracting an archive from the internet. COMMUNITY.
Disk usage
- VERIFIED (tldr du):
du -sh DIRtotal of one folder;du -h -d 1 DIRone level down. - VERIFIED (tldr df):
dfshows filesystem space. UNVERIFIED:df -hfor human sizes. - VERIFIED (tldr ncdu):
ncduorncdu DIRis an interactive size browser. UNVERIFIED: delete key inside ncdu; read before pressing. du -h -d 1 ~ | sort -hfinds the big folders.sort -his UNVERIFIED.
Processes
- VERIFIED (tldr ps):
ps aux;ps aux | grep [s]tring(the brackets stop grep matching itself). - VERIFIED (tldr htop):
htoplive view;htop -u name; F1 or ? for help.topis the built-in older tool (UNVERIFIED details). - VERIFIED (man7 kill, tldr kill): kill sends TERM by default, which lets the program clean up. Use KILL (-9) only if TERM fails.
kill -llists signals.kill %1stops background job 1. - VERIFIED (tldr pgrep, pkill):
pgrep -a namefinds PIDs;pkill namesignals by name. Runpgrep -a namefirst to see what pkill would hit. - Never kill a process you cannot name. Never
kill -9 1or kill the desktop session by guess.
Network tools
- VERIFIED (tldr curl):
curl URLprints;curl -L -O URLfollows redirects and saves;-vverbose.-kskips certificate checks: avoid. - VERIFIED (tldr wget):
wget URL;-O file;-ccontinues an interrupted download. - VERIFIED (man7 ss):
ss -tulnpis the usual combination: TCP, UDP, listening, numeric, show process (each flag read separately). Process names for other users need sudo (UNVERIFIED). - VERIFIED (tldr ping):
ping -c 4 hoststops after 4. - VERIFIED (tldr dig):
dig +short example.com;dig +short example.com MX;dig @1.1.1.1 example.comasks a chosen DNS server. - Order for "no internet": ping a router IP, ping 1.1.1.1, ping a name, dig the name. COMMUNITY.
- Check a download before running it:
sha256sum fileand compare to the site's published hash. UNVERIFIED.
Packages on Bazzite and distrobox
- VERIFIED (Bazzite docs): Flatpak (Bazaar app store) for apps; Homebrew for command-line tools; Distrobox for other Linux apps; rpm-ostree layering is discouraged "if possible".
- VERIFIED (Flatpak docs):
flatpak search NAME,flatpak install flathub ID,flatpak run ID,flatpak list --app,flatpak update,flatpak uninstall ID. - VERIFIED (rpm-ostree handbook):
rpm-ostree statuslists deployments;upgradestages an update for next boot;install PKGlayers a package and needs a reboot;uninstall PKGremoves it;rollbackswaps back to the previous deployment (reboot to boot it). - VERIFIED (Bazzite docs):
rpm-ostree rollbackand the Bazzite Rollback Helper exist.ujust updateis UNVERIFIED on the docs page. - VERIFIED (distrobox.it):
distrobox create -n test,distrobox enter test,distrobox list,distrobox rm test. Containers share your home folder. dnfdoes not install into the Bazzite base system. Inside a distrobox it works on the container (COMMUNITY).- Look for the Flatpak or brew version first. Layering last.
Safe habits
- Read before running. Paste unknown commands into explainshell.com (VERIFIED: it matches each argument to its help text) or
man cmdfirst. - Never
curl ... | bashorsudosomething from a forum without understanding it. COMMUNITY. - Dry run:
rsync --dry-run,ls PATTERNbeforerm PATTERN,findwithout-deletefirst,echo rm -rf "$dir"to see what a variable expands to. - Backup before bulk edits:
cp -a dir dir.bak, orsedwithout-i, ortar czfof the folder. - Use full paths and quotes. Check
pwdbefore relative deletes. - One change, test, then the next. Keep the old command text in history.
- Use
--before names that start with-(VERIFIED in the Quotes page examplecp -- "$src" "$dest"). - Reddit r/commandline and r/bash were blocked, so no community-rule claims here.
Commands that can wipe your own data (a safety list, for protecting yourself)
COMMUNITY unless marked.
rm -rfanything, especially with variables,*,/,~or...chmod -Rorchown -Ron system folders;chmod 777.> fileon an important file (VERIFIED: truncates it).sed -iwithout a backup.dd if=... of=/dev/...: writes raw to a disk. Wrong target wipes it.mkfs,fdisk,parted,wipefson the wrong device. Checklsblkfirst (UNVERIFIED).kill -9,pkillwith a loose name;sudowith anything you did not read.curl URL | shor| sudo bash.- Any unknown one-liner pasted from a forum or chat: read it first and ask what each part does before running.
find ... -deleteor-exec rmwithout a dry run (VERIFIED -delete exists).rpm-ostreechanges without knowing rollback;systemctl disableon system units you did not name.
Worked examples (build up one step at a time)
- Find which log lines mention an error, newest last. Commands VERIFIED individually (tldr grep, tail, sort, uniq):
- Step 1:
tail -n 200 file.log(look first). - Step 2:
grep -i "error" file.log | tail -n 20. - Step 3:
grep -i "error" file.log | sort | uniq -c | sort -nr | head(most common errors).
- Step 1:
- Find big files in Downloads, then decide by hand:
du -ah ~/Downloads | sort -h | tail -n 15(sort -hUNVERIFIED), orncdu ~/Downloads(VERIFIED).
- Rename many files safely (COMMUNITY pattern, loop VERIFIED in GNU Looping page):
- Step 1:
for f in *.wav; do echo mv -n -- "$f" "new_$f"; done(echo only prints). - Step 2: remove
echoonly when the printed list looks right.
- Step 1:
- Search a project for a word and open the hit:
rg -n "word", thenless +NUMBER file(UNVERIFIED+N). - Save command output and errors for a bug report:
cmd > out.txt 2>&1(VERIFIED order), thenless out.txt. - Run a long copy that survives a closed laptop lid or dropped ssh:
tmux new -s copy, run rsync inside,Ctrl+B d(VERIFIED).
Troubleshooting trees
"command not found":
- Check spelling and case. Tab-complete it.
command -v NAME(UNVERIFIED) shows if it exists. Nothing printed means not on PATH.- Script in the current folder? Use
./NAME(COMMUNITY). - Not installed? Order: Flatpak, brew, distrobox, then layering (VERIFIED Bazzite docs).
- Installed by brew just now? Open a new terminal so PATH reloads (COMMUNITY).
"Permission denied":
ls -l FILEandwhoami(read-only, VERIFIED ls).- Script without execute bit?
chmod u+x FILE(VERIFIED tldr). - Folder you do not own? Do not chmod -R it. Ask why first.
- Only then consider
sudofor that single command (VERIFIED tldr sudo).
"No such file or directory":
pwdandls. Wrong folder is the usual cause.- Spaces in the name? Quote it (VERIFIED Quotes page).
- A glob that matched nothing stays literal, so
ls *.cfails (VERIFIED glob page). - Windows line ends in a script (
^M)?tr -d '\r' < in > out(VERIFIED tr flag; cause is COMMUNITY).
Command seems stuck:
- Is it waiting for input? Ctrl+D ends input. Ctrl+C interrupts (COMMUNITY).
- Stopped by accident (Ctrl+Z)?
jobs, thenfg(VERIFIED). - Still stuck? Another terminal:
pgrep -a NAME, thenkill PID, and only laterkill -9 PID(VERIFIED man7 kill).
Disk full:
df -hto find the full filesystem.du -h -d 1 ~ | sort -horncdu ~to find the cause.- Flatpak leftovers and old container data are common causes (UNVERIFIED); do not delete by guess.
ssh will not connect:
ssh -v user@hostand read the last lines (VERIFIED -v).ping host, thendig +short host(VERIFIED) to split network from DNS.- Wrong port?
-p PORT(VERIFIED). Wrong key?-i FILE(VERIFIED). - Host key changed warning: stop and confirm with the server owner (VERIFIED warning exists).
Output scrolls away: pipe to less, or cmd 2>&1 | less for errors too (VERIFIED redirect semantics, COMMUNITY habit).
Weird characters after a binary file was printed: type reset and press Enter (UNVERIFIED).
Cheat sheet: 40 commands
pwd, ls -la, cd, mkdir -p, cp -iv, mv -iv, rm -v (after ls), ln -s, find -name, locate, cat, less, head, tail -f, grep -rn, rg, sed 's///', awk '{print $1}', sort, uniq -c, cut -d -f, tr, wc -l, diff -u, tee, xargs (UNVERIFIED), history, chmod u+x, sudo, tar czf / xf, zip/unzip, du -sh, df -h, ncdu, ps aux, htop, kill, pgrep -a, curl -L -O, ss -tulnp, ping -c 4, dig +short, ssh, rsync -a --dry-run, tmux, flatpak, brew, distrobox, rpm-ostree status, shellcheck. (All have a VERIFIED tldr or man7 line above except those marked UNVERIFIED.)
Not verified
- GNU Bash manual pages Pipelines, Shell-Variables, Commands-For-History and the single-page manual failed to fetch. PATH, PS1 and Ctrl+R details are from memory.
- GNU coreutils rm page failed; rm flags such as -I are UNVERIFIED.
- Konsole manual (docs.kde.org) failed; only UserBase tab notes were read. Copy/paste and split-view keys UNVERIFIED.
- Fedora docs returned Access Denied. No dnf/Fedora claims verified.
- Reddit r/commandline and r/bash blocked. explainshell was read only for its description, not for sample output.
- zsh and fish behaviour not fetched. Bazzite default shell,
ujustcommands,brewusage, cron/cronie availability, user systemd timers,trash-cli,ssroot requirement,df -h,sort -h,sha256sumare UNVERIFIED. - Greg's Wiki BashFAQ on
set -epitfalls was not read. - Man pages are not Bazzite-specific; versions on the reader's machine may differ.
Sources (fetched)
- GNU Bash manual: gnu.org/software/bash/manual/html_node/ (The-Set-Builtin, Redirections, Bash-History-Facilities, Commands-For-Moving, Commands-For-Killing, Job-Control-Basics, Shell-Functions, Looping-Constructs, Event-Designators)
- GNU coreutils: cp-invocation, mv-invocation
- Greg's Wiki: mywiki.wooledge.org/BashGuide, /Quotes, /glob, /ParsingLs
- man7.org: tmux(1), crontab(5), systemd.timer(5), ssh(1), chmod(1), ss(8), kill(1)
- tldr pages (raw.githubusercontent.com/tldr-pages/tldr): tar, find, ncdu, distrobox, curl, wget, du, df, grep, sed, awk, dig, ping, ps, htop, tail, tmux, screen, cut, tr, sort, uniq, diff, rsync, rg, locate, less, head, wc, cat, ls, cd, mkdir, ln, chmod, chown, sudo, history, kill, pkill, pgrep, nohup, fd, gzip, zip, unzip, xz
- ShellCheck: github.com/koalaman/shellcheck and its wiki, SC2086
- explainshell.com (home page)
- Fedora/Red Hat: coreos.github.io/rpm-ostree/administrator-handbook/
- Bazzite docs: docs.bazzite.gg (home, Installing_and_Managing_Software, Updates_Rollbacks_and_Rebasing)
- distrobox.it; docs.flatpak.org/en/latest/using-flatpak.html; userbase.kde.org/Konsole
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

