Essential Shell Script Best Practices for Reliable Automation

Whether for system or application operations, the workflow progresses from "pure manual" → "scripted" → "automated" → "intelligent". In the automation stage, repetitive tasks are encapsulated in scripts, reducing risk and improving efficiency. Shell scripts are the most common tool for this transition.

1) Script Header Information

The script should start with a comment block that describes its purpose, usage of parameters, author, creation/modification dates, and version, following a standard format.

2) Formatting and Alignment

Maintain consistent indentation for loops, conditionals, and case statements to improve readability.

3) Strict Error Handling

Enable strict mode (e.g., set -euo pipefail) so that undefined variables or non‑zero exit codes cause the script to abort immediately.

4) Quote All Parameters

Wrap every command‑line argument in single or double quotes, especially for destructive commands like rm and mv. Adopt a trash‑can strategy: move files to a temporary directory before deletion.

5) Wildcard Usage

Prefer precise patterns; avoid using * when the exact prefix, suffix, or extension is known. Use ? for single‑character matches.

6) Ensure Numeric Variables Remain Numeric

Validate that variables intended to hold numbers are indeed numeric before performing arithmetic.

7) Quote Variables in Test Expressions

Always place variables inside double quotes within [ ] tests to prevent word splitting.

8) Use Relative Paths for Archiving

When creating tar archives, use relative paths; never embed absolute paths.

9) Pipe Operations Should Not Read and Write the Same File

Never read from and write to the same file in a single pipeline; instead write to a temporary file and then move it.

10) Verify Return Values of cd

Always check the exit status of cd before executing subsequent commands; use logical operators ( ||, &&) as needed.

Additional Practical Tips

• Use expect or curl for interactive scripts and file transfers.

# FTP download example
curl -u ftpuser:ftppassword -O "sftp://ftp_ip:ftp_port/pathfile"

# FTP upload example
curl -u ftpuser:ftppassword --ftp-create-dirs -T upfile "sftp://ftp_ip:ftp_port/filepath/upfile"

• Include usage help and logging in scripts to aid troubleshooting.

• Implement file‑locking mechanisms to prevent concurrent executions.

• Guard against scripts hanging by adding timeout logic.

• Distribute load when publishing scripts to avoid bottlenecks on storage or network resources.

• Set size limits for log or data files and rotate/clean them regularly.

Conclusion

By following standardized headers, clear formatting, strict error handling, proper quoting, safe file operations, and incorporating logging, concurrency control, and risk‑mitigation strategies, shell scripts become reliable building blocks for automated and intelligent operations.