How to Write Robust Shell Scripts: Essential Tips and Best Practices

Syntax Checking

Use a static analysis tool such as shellcheck to detect syntax errors early; it catches most common mistakes before the script runs.

Exit on Failure (set -e)

Place set -e at the top of the script so that any command returning a non‑zero status aborts the script. set -e Example:

#!/bin/bash
set -e
lp    # this command fails
date

If a command is expected to fail but you want the script to continue, append || true to that command, or later disable the option with set +e.

set -e
lp || true
date

Print Execution Trace (set -x)

Run the script with sh -x script.sh or add set -x at the beginning to see each command as it is executed.

sh -x test.sh

#!/bin/bash
set -x
if [ $# -lt 1 ]; then
  echo "no para"
else
  echo "para 1 $1"
fi

The output shows commands prefixed with +, revealing variable expansions and branch decisions.

Detect Undefined Variables (set -u)

Enable set -u to treat the use of an unset variable as an error. set -u Running the previous example with set -u produces an error message indicating the undefined variable.

Fail the Whole Pipeline (set -o pipefail)

When a pipeline contains multiple commands, set -o pipefail makes the pipeline return a non‑zero status if any component fails.

set -o pipefail
cat test.sh | grep if | cut -d ';' -f 2

Make Static Variables Read‑Only

Declare constants with readonly to prevent accidental modification.

MY_PATH=/usr/bin
readonly MY_PATH=/usr/bin
MY_PATH=/usr/local/bin   # triggers an error

Provide Optional Default Values

Use parameter expansion to assign a fallback when a variable is empty or unset.

name=${1:-shouwang}
echo "$name"

Chain Commands with &&

Replace semicolon‑separated commands with && so that subsequent commands run only if the previous one succeeds.

cmd0 && cmd1 && cmd2

Use Functions for Larger Scripts

Encapsulate reusable logic in functions to improve readability and maintainability as scripts grow.

Summary

Static analysis tools like shellcheck catch most syntax problems, while the set options ( -e, -u, -x, -o pipefail) and best‑practice patterns (readonly constants, default values, command chaining, functions) together make Bash scripts robust and easier to debug.