Bash Rules

Write portable shell scripts by avoiding bashisms when targeting /bin/sh, using POSIX-compliant constructs, and clearly declaring the required shell in the shebang line.

Every variable expansion and command substitution in Bash must be double-quoted to prevent word splitting, glob expansion, and catastrophic bugs with filenames containing spaces.

All Bash scripts must pass ShellCheck static analysis with zero warnings — catch quoting bugs, deprecated syntax, and portability issues before they reach production.

Every Bash script must begin with strict mode flags — set -euo pipefail — to catch errors early, prevent undefined variable usage, and propagate pipeline failures.

Enforce consistent variable naming in Bash — lowercase snake_case for locals, UPPER_SNAKE_CASE for exports, readonly for constants, and local declarations inside functions.