shell-scripting

Robust Bash scripts start with safe defaults: use set -euo pipefail to exit on errors, undefined variables, and pipe failures. Add proper quoting around variables, structure code into functions, include a usage function for help text, and implement error handling to catch and report failures clearly.

Maintainable shell scripts follow these practices: use meaningful variable names, organize code with functions, quote all variable expansions, avoid parsing ls output, handle errors explicitly, include usage documentation, and apply safe defaults like set -euo pipefail from the start.

Modern tools like rg (ripgrep), fd, fzf, jq, and yq replace slower traditional commands in shell scripts. They integrate seamlessly into pipelines for fast file searching, filtering, and JSON/YAML processing. Use them in place of grep, find, and awk for better performance and cleaner syntax.

Yes. Both Bash and Zsh support the core safety practices: set -euo pipefail, proper quoting, function-based organization, and error handling. This Skill covers techniques that work across both shells, ensuring your scripts remain robust and portable.

Structure scripts with a proper shebang, safe defaults at the top, a usage function for documentation, modular functions for each task, clear error handling, and meaningful variable names. This approach makes scripts readable, debuggable, and reusable across pipelines and tooling integrations.

Parsing ls is unsafe: filenames with spaces, special characters, or permissions changes break parsing logic. Modern tools like fd and find provide reliable alternatives that handle edge cases correctly and integrate better into robust automation workflows.