Bash Script Style Guide

• Use #!/usr/bin/env bash as shebang
• Always use set -euo pipefail for safety
• Keep scripts minimal: no unnecessary comments or echoes
• Minimal input validation; print usage to stderr and exit if inputs are missing/invalid
• Don't check for installed commands if failure is obvious on use
• Make script executable: chmod +x <script>
• Prefer concise, direct logic over verbosity