shell-scripting

What it does and when to use it

Write robust, safe bash/shell scripts and one-liners, and explain or fix existing ones. Use when users want a shell script, a command pipeline, automation glue, or ask why a bash snippet misbehaves (quoting, globbing, exit codes). Triggers on mentions of bash, shell script, .sh, command line, pipe, one-liner, cron job command, 脚本, 命令行, 管道, shell.

How it works

1. Start every script with a strict header
2. Quoting & safety (the top source of bugs)
3. Common patterns
4. Guidance

---
name: shell-scripting
description: "Write robust, safe bash/shell scripts and one-liners, and explain or fix existing ones. Use when users want a shell script, a command pipeline, automation glue, or ask why a bash snippet misbehaves (quoting, globbing, exit codes). Triggers on mentions of bash, shell script, .sh, command line, pipe, one-liner, cron job command, 脚本, 命令行, 管道, shell."
license: Proprietary. LICENSE.txt has complete terms
compatibility: "No external dependencies. Works on macOS, Linux, and Windows (WSL/Git Bash)."
---

# Shell Scripting

Write scripts that fail loudly and safely, not ones that silently do the wrong thing.

## Start every script with a strict header

```bash
#!/usr/bin/env bash
set -euo pipefail   # exit on error, error on unset var, fail a pipeline if any stage fails
IFS=$'\n\t'
```

## Quoting & safety (the top source of bugs)

- Always quote expansions: `"$var"`, `"${arr[@]}"`, `"$(cmd)"` — unquoted values word-split and glob.
- Use `[[ ... ]]` over `[ ... ]` for tests; `(( ... ))` for arithmetic.
- Prefer `"$(cmd)"` over backticks. Check `mkdir -p`, `rm -rf` paths twice.
- Handle filenames with spaces/newlines: `find ... -print0 | xargs -0`, or `while IFS= read -r line`.

## Common patterns

```bash
# Args with defaults
name="${1:-world}"

# Loop over files safely
for f in ./*.log; do [[ -e "$f" ]] || continue; echo "$f"; done

# Trap cleanup on exit
tmp="$(mktemp)"; trap 'rm -f "$tmp"' EXIT

# Check a command exists
command -v jq >/dev/null 2>&1 || { echo "jq required" >&2; exit 1; }
```

## Guidance

- Run `shellcheck script.sh` if available — it catches most real bugs.
- Make scripts idempotent where possible; print what they're doing.
- Don't parse `ls` output; glob or use `find`. Don't `eval` untrusted input.
- For anything beyond ~50 lines of logic, consider Python instead.

Versions

Database snapshot: 13.11.2026 · package version 9488e3219f31 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100overview
  Cross-language CLI and scripting guidance for IT automation, system administration, and DevOps workflows: language selection (Bash vs PowerShell vs Python vs Node.js), pipes, exit codes, environment variables, argument parsing, error handling, and cross-platform scripting best…
• 100bash-expert
  Expert Bash help for writing, debugging, and optimizing safe, portable shell one-liners and scripts on macOS/Linux. Use when users ask for Bash or POSIX sh commands, script reviews, ShellCheck fixes, quoting/pipeline issues, process/file automation, or converting requirements into shell scripts.
• 100linux-bash-scripting
  Defensive Bash scripting for Linux: safe foundations, argument parsing, production patterns, ShellCheck compliance. Use when writing "bash script", "shell script", "linux automation", "system script", "cron job", "deployment script", "CLI tool in bash", or "automate with bash".
• 100shell-expert
  Shell scripting expertise, command-line tools, automation, and cross-platform scripting best practices. Covers shell script development, CLI tool usage, and system automation with bash, zsh, and POSIX shell. Use when user mentions shell scripts, bash, zsh, CLI commands, pipes,…
• 100bash-scripting-expert
  Expert Bash scripting: robust, safe, portable shell scripts. Trigger keywords: bash, shell script, sh, quoting, word splitting, set -euo pipefail, trap, IFS, getopts, mktemp, shellcheck, POSIX, CLI, automation. Use for writing/debugging shell scripts and automation, or fixing…
• 95bash-script-generator
  Creates bash scripts with argument parsing, error handling, logging, and input validation following current standards. Use when creating new bash or shell scripts, .sh files, CLI tools, scripting automation, text processing workflows (grep/awk/sed pipelines), or building…