Describe What You Need and Let Claude Write the Shell One-Liner

Shell commands are powerful but the syntax is brutal — was it -mtime or -mmin? Does xargs need -I {} or -0? Instead of Googling, describe what you want and let Claude write and test the command.

Find all log files in /var/log that are larger than 100MB 
and were modified in the last 7 days. Sort by size, largest first.

Claude writes the command, runs it on your machine, and shows you the output:

find /var/log -name "*.log" -size +100M -mtime -7 -exec ls -lhS {} +

If the result isn't quite right, just describe the correction:

That's close but I also need to include .gz files and show the total size at the end.

Claude adjusts the command and runs it again. This iterative loop is faster than reading man pages.

Common shell tasks that are hard to remember but easy to describe:

# File operations
Move all PNG files from Downloads into folders named by year-month based on their creation date

# Text processing
Extract all unique email-like patterns from access.log and count how many times each appears

# Process management
Find all Node processes using more than 500MB of memory and show their command lines

# Disk analysis
Show the 20 largest directories under /home, with human-readable sizes

# Network
List all open ports and which process is listening on each one

Claude also explains what each part does, so you learn the syntax while getting the answer:

Explain this command before running it:
awk '{print $1}' access.log | sort | uniq -c | sort -rn | head -20

For commands you'll reuse, ask Claude to add them as shell aliases or functions in your profile.

Shell commands are a write-only language — describe the intent in English, let Claude write the syntax, and learn from the explanation.

via Claude Code