
Bash Linux
Apply vetted Bash patterns for chaining, files, processes, and text processing on Linux and macOS while coding or debugging locally.
Overview
Bash Linux is a journey-wide agent skill that documents critical Bash and Linux/macOS terminal commands, piping, and scripting patterns—usable whenever a solo builder needs reliable shell operations before committing to
Install
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill bash-linuxWhat is this skill?
- Operator cheat sheet: ;, &&, ||, and pipes for command chaining
- File and search commands: find, grep -r, tail -f, du, df
- Process and port recipes: ps, lsof, kill -9, background jobs
- Text processing with core CLI tools referenced in SKILL.md
- macOS and Linux terminal workflows for daily development
- 4 major pattern sections: operators, files, processes, text processing
Adoption & trust: 1.3k installs on skills.sh; 40.1k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent keeps inventing wrong shell flags or unsafe kill patterns when you work on Linux or macOS.
Who is it for?
Solo builders who live in integrated terminals on Mac or Linux and want consistent agent answers for everyday Dev tasks.
Skip if: Windows PowerShell-only workflows or deep production bash frameworks that need full shellcheck-tested scripts.
When should I use this skill?
Working on macOS or Linux systems needing Bash/Linux terminal patterns, piping, error handling, or scripting.
What do I get? / Deliverables
You get table-driven Bash patterns for chaining, files, processes, and text tools that agents can cite during build, ship, and operate tasks.
- Correct shell command snippets
- Process and port troubleshooting steps
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Chain migrations and server start with && after pulling main on Linux.
Pipe test output through grep to isolate failing suites in CI logs.
Use tail -f and lsof to debug a crashed Node process binding port 3000.
Quick find and du checks to understand a cloned prototype repo size and layout.
How it compares
Compact pattern reference skill—not a Terraform deploy pack or a packaged MCP shell server.
Common Questions / FAQ
Who is bash-linux for?
Indie developers and agent users on macOS or Linux who need dependable terminal command patterns during coding and ops.
When should I use bash-linux?
Use during Build for dev servers and grep/find tasks, during Ship for log tailing and test chains, and during Operate for port conflicts and process kills—any time shell work is on the critical path.
Is bash-linux safe to install?
The skill documents destructive commands like kill -9; review the Security Audits panel on this page and never auto-run shell without reading the suggested command.
SKILL.md
READMESKILL.md - Bash Linux
# Bash Linux Patterns > Essential patterns for Bash on Linux/macOS. --- ## 1. Operator Syntax ### Chaining Commands | Operator | Meaning | Example | |----------|---------|---------| | `;` | Run sequentially | `cmd1; cmd2` | | `&&` | Run if previous succeeded | `npm install && npm run dev` | | `\|\|` | Run if previous failed | `npm test \|\| echo "Tests failed"` | | `\|` | Pipe output | `ls \| grep ".js"` | --- ## 2. File Operations ### Essential Commands | Task | Command | |------|---------| | List all | `ls -la` | | Find files | `find . -name "*.js" -type f` | | File content | `cat file.txt` | | First N lines | `head -n 20 file.txt` | | Last N lines | `tail -n 20 file.txt` | | Follow log | `tail -f log.txt` | | Search in files | `grep -r "pattern" --include="*.js"` | | File size | `du -sh *` | | Disk usage | `df -h` | --- ## 3. Process Management | Task | Command | |------|---------| | List processes | `ps aux` | | Find by name | `ps aux \| grep node` | | Kill by PID | `kill -9 <PID>` | | Find port user | `lsof -i :3000` | | Kill port | `kill -9 $(lsof -t -i :3000)` | | Background | `npm run dev &` | | Jobs | `jobs -l` | | Bring to front | `fg %1` | --- ## 4. Text Processing ### Core Tools | Tool | Purpose | Example | |------|---------|---------| | `grep` | Search | `grep -rn "TODO" src/` | | `sed` | Replace | `sed -i 's/old/new/g' file.txt` | | `awk` | Extract columns | `awk '{print $1}' file.txt` | | `cut` | Cut fields | `cut -d',' -f1 data.csv` | | `sort` | Sort lines | `sort -u file.txt` | | `uniq` | Unique lines | `sort file.txt \| uniq -c` | | `wc` | Count | `wc -l file.txt` | --- ## 5. Environment Variables | Task | Command | |------|---------| | View all | `env` or `printenv` | | View one | `echo $PATH` | | Set temporary | `export VAR="value"` | | Set in script | `VAR="value" command` | | Add to PATH | `export PATH="$PATH:/new/path"` | --- ## 6. Network | Task | Command | |------|---------| | Download | `curl -O https://example.com/file` | | API request | `curl -X GET https://api.example.com` | | POST JSON | `curl -X POST -H "Content-Type: application/json" -d '{"key":"value"}' URL` | | Check port | `nc -zv localhost 3000` | | Network info | `ifconfig` or `ip addr` | --- ## 7. Script Template ```bash #!/bin/bash set -euo pipefail # Exit on error, undefined var, pipe fail # Colors (optional) RED='\033[0;31m' GREEN='\033[0;32m' NC='\033[0m' # Script directory SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" # Functions log_info() { echo -e "${GREEN}[INFO]${NC} $1"; } log_error() { echo -e "${RED}[ERROR]${NC} $1" >&2; } # Main main() { log_info "Starting..." # Your logic here log_info "Done!" } main "$@" ``` --- ## 8. Common Patterns ### Check if command exists ```bash if command -v node &> /dev/null; then echo "Node is installed" fi ``` ### Default variable value ```bash NAME=${1:-"default_value"} ``` ### Read file line by line ```bash while IFS= read -r line; do echo "$line" done < file.txt ``` ### Loop over files ```bash for file in *.js; do echo "Processing $file" done ``` --- ## 9. Differences from PowerShell | Task | PowerShell | Bash | |------|------------|------| | List files | `Get-ChildItem` | `ls -la` | | Find files | `Get-ChildItem -Recurse` | `find . -type f` | | Environment | `$env:VAR` | `$VAR` | | String concat | `"$a$b"` | `"$a$b"` (same) | | Null check | `if ($x)` | `if [ -n "$x" ]` | | Pipeline | Object-based | Text-based | --- ## 10. Error Handling ### Set options ```bash set -e # Exit on error set -u # Exit on undefined variable set -o pipefail # Exit on pipe failure set -x # Debug: print commands ``` ### Trap for cleanup ```bash cleanup() { echo "Cleaning up..."