bash-defensive-patterns

Strict mode uses set -Eeuo pipefail to catch errors immediately. -E inherits error traps, -e exits on errors, -u fails on undefined variables, -o pipefail catches failures in pipes. Add this at the top of your script to prevent silent failures and hard-to-debug behavior in production automation.

Use trap handlers to run cleanup code when errors occur. Set traps before executing risky commands to capture exit codes, log failures, and release resources. Combined with strict mode, traps ensure your script fails predictably and leaves no dangling processes or incomplete state.

Unquoted variables split on whitespace and expand glob patterns, causing arguments to scatter into separate words. Quoting variables like "$var" and using arrays preserve word boundaries and prevent injection attacks, making scripts robust across filenames with spaces and special characters.

Idempotent design means repeating a script produces the same result without side effects. Check for existing state before creating files or directories, use atomic operations, and structure tasks so re-running is safe. This is critical for cron jobs, orchestration, and disaster recovery.

Yes. Apply strict mode to existing scripts to surface hidden errors, add error traps to see where failures occur, and add set -x for execution tracing. Defensive patterns expose bugs that silent failures masked, making debugging faster and preventing production outages.

No, but defensive patterns matter. Use explicit loops with shift or getopts, validate argument count and types, quote expansions, and document expected inputs. Robust argument handling prevents malformed input from breaking scripts and makes automation reliable across environments.