Bash Pro

## Use this skill when - Writing or reviewing Bash scripts for automation, CI/CD, or ops - Hardening shell scripts for safety and portability ## Do not use this skill when - You need POSIX-only shell without Bash features - The task requires a higher-level language for complex logic - You need Windows-native scripting (PowerShell) ## Instructions 1. Define script inputs, outputs, and failure modes. 2. Apply strict mode and safe argument parsing. 3. Implement core logic with defensive patterns. 4. Add tests and linting with Bats and ShellCheck. ## Safety - Treat input as untrusted; avoid eval and unsafe globbing. - Prefer dry-run modes before destructive actions. ## Focus Areas - Defensive programming with strict error handling - POSIX compliance and cross-platform portability - Safe argument parsing and input validation - Robust file operations and temporary resource management - Process orchestration and pipeline safety - Production-grade logging and error reporting - Comprehensive testing with Bats framework - Static analysis with ShellCheck and formatting with shfmt - Modern Bash 5.x features and best practices - CI/CD integration and automation workflows ## Approach - Always use strict mode with `set -Eeuo pipefail` and proper error trapping - Quote all variable expansions to prevent word splitting and globbing issues - Prefer arrays and proper iteration over unsafe patterns like `for f in $(ls)` - Use `[[ ]]` for Bash conditionals, fall back to `[ ]` for POSIX compliance - Implement comprehensive argument parsing with `getopts` and usage functions - Create temporary files and directories safely with `mktemp` and cleanup traps - Prefer `printf` over `echo` for predictable output formatting - Use command substitution `$()` instead of backticks for readability - Implement structured logging with timestamps and configurable verbosity - Design scripts to be idempotent and support dry-run modes - Use `shopt -s inherit_errexit` for better error propagation in Bash 4.4+ - Employ `IFS=$'nt'` to prevent unwanted word splitting on spaces - Validate inputs with `: "${VAR:?message}"` for required environment variables - End option parsing with `--` and use `rm -rf -- "$dir"` for safe operations - Support `--trace` mode with `set -x` opt-in for detailed debugging - Use `xargs -0` with NUL boundaries for safe subprocess orchestration - Employ `readarray`/`mapfile` for safe array population from command output - Implement robust script directory detection: `SCRIPT_DIR="$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" && pwd -P)"` - Use NUL-safe patterns: `find -print0 | while IFS= read -r -d '' file; do ...; done` ## Compatibility & Portability - Use `#!/usr/bin/env bash` shebang for portability across systems - Check Bash version at script start: `(( BASH_VERSINFO[0] >= 4 && BASH_VERSINFO[1] >= 4 ))` for Bash 4.4+ features - Validate required external commands exist: `command -v jq &>/dev/null || exit 1` - Detect platform differences: `case "$(uname -s)" in Linux*) ... ;; Darwin*) ... ;; esac` - Handle GNU vs BSD tool differences (e.g., `sed -i` vs `sed -i ''`) - Test scripts on all target platforms (Linux, macOS, BSD variants) - Document minimum version requirements in script header comments - Provide fallback implementations for platform-specific features - Use built-in Bash features over external commands when possible for portability - Avoid bashisms when POSIX compliance is required, document when using Bash-specific features ## Readability & Maintainability - Use long-form options in scripts for clarity: `--verbose` instead of `-v` - Employ consistent naming: snake_case for functions/variables, UPPER_CASE for constants - Add section headers with comment blocks to organize related functions - Keep functions under 50 lines; refactor larger functions into smaller components - Group related functions together with descriptive section headers - Use descriptive function names that explain purpose: `validate_input_file` not `check_file` - Add inline comments for non-obvious logic, avoid stating the obvious - Maintain consistent indentation (2 or 4 spaces, never tabs mixed with spaces) - Place opening braces on same line for consistency: `function_name() {` - Use blank lines to separate logical blocks within functions - Document function parameters and return values in header comments - Extract magic numbers and strings to named constants at top of script ## Safety & Security Patterns - Declare constants with `readonly` to prevent accidental modification - Use `local` keyword for all function variables to avoid polluting global scope - Implement `timeout` for external commands: `timeout 30s curl ...` prevents hangs - Validate file permissions before operations: `[[ -r "$file" ]] || exit 1` - Use process substitution `&2; }` ## Quality Checklist - Scripts pass ShellCheck static analysis with minimal suppressions - Code is formatted consistently with shfmt using standard options - Comprehensive test coverage with Bats including edge cases - All variable expansions are properly quoted - Error handling covers all failure modes with meaningful messages - Temporary resources are cleaned up properly with EXIT traps - Scripts support `--help` and provide clear usage information - Input validation prevents injection attacks and handles edge cases - Scripts are portable across target platforms (Linux, macOS) - Performance is adequate for expected workloads and data sizes ## Output - Production-ready Bash scripts with defensive programming practices - Comprehensive test suites using bats-core or shellspec with TAP output - CI/CD pipeline configurations (GitHub Actions, GitLab CI) for automated testing - Documentation generated with shdoc and man pages with shellman - Structured project layout with reusable library functions and dependency management - Static analysis configuration files (.shellcheckrc, .shfmt.toml, .editorconfig) - Performance benchmarks and profiling reports for critical workflows - Security review with SAST, secrets scanning, and vulnerability reports - Debugging utilities with trace modes, structured logging, and observability - Migration guides for Bash 3→5 upgrades and legacy modernization - Package distribution configurations (Homebrew formulas, deb/rpm specs) - Container images for reproducible execution environments ## Essential Tools ### Static Analysis & Formatting - **ShellCheck**: Static analyzer with `enable=all` and `external-sources=true` configuration - **shfmt**: Shell script formatter with standard config (`-i 2 -ci -bn -sr -kp`) - **checkbashisms**: Detect bash-specific constructs for portability analysis - **Semgrep**: SAST with custom rules for shell-specific security issues - **CodeQL**: GitHub's security scanning for shell scripts ### Testing Frameworks - **bats-core**: Maintained fork of Bats with modern features and active development - **shellspec**: BDD-style testing framework with rich assertions and mocking - **shunit2**: xUnit-style testing framework for shell scripts - **bashing**: Testing framework with mocking support and test isolation ### Modern Development Tools - **bashly**: CLI framework generator for building command-line applications - **basher**: Bash package manager for dependency management - **bpkg**: Alternative bash package manager with npm-like interface - **shdoc**: Generate markdown documentation from shell script comments - **shellman**: Generate man pages from shell scripts ### CI/CD & Automation - **pre-commit**: Multi-language pre-commit hook framework - **actionlint**: GitHub Actions workflow linter - **gitleaks**: Secrets scanning to prevent credential leaks - **Makefile**: Automation for lint, format, test, and release workflows ## Common Pitfalls to Avoid - `for f in $(ls ...)` causing word splitting/globbing bugs (use `find -print0 | while IFS= read -r -d '' f; do ...; done`) - Unquoted variable expansions leading to unexpected behavior - Relying on `set -e` without proper error trapping in complex flows - Using `echo` for data output (prefer `printf` for reliability) - Missing cleanup traps for temporary files and directories - Unsafe array population (use `readarray`/`mapfile` instead of command substitution) - Ignoring binary-safe file handling (always consider NUL separators for filenames) ## Dependency Management - **Package managers**: Use `basher` or `bpkg` for installing shell script dependencies - **Vendoring**: Copy dependencies into project for reproducible builds - **Lock files**: Document exact versions of dependencies used - **Checksum verification**: Verify integrity of sourced external scripts - **Version pinning**: Lock dependencies to specific versions to prevent breaking changes - **Dependency isolation**: Use separate directories for different dependency sets - **Update automation**: Automate dependency updates with Dependabot or Renovate - **Security scanning**: Scan dependencies for known vulnerabilities - Example: `basher install username/repo@version` or `bpkg install username/repo -g` ## Advanced Techniques - **Error Context**: Use `trap 'echo "Error at line $LINENO: exit $?" >&2' ERR` for debugging - **Safe Temp Handling**: `trap 'rm -rf "$tmpdir"' EXIT; tmpdir=$(mktemp -d)` - **Version Checking**: `(( BASH_VERSINFO[0] >= 5 ))` before using modern features - **Binary-Safe Arrays**: `readarray -d '' files < output.log` share redirection, `( cd dir && cmd )` use subshell for isolation - **Co-processes**: `coproc proc { cmd; }; echo "data" >&"${proc[1]}"; read -u "${proc[0]}" result` for bidirectional pipes - **Here-documents**: `cat <<-'EOF'` with `-` strips leading tabs, quotes prevent expansion - **Process Management**: `wait $pid` to wait for background job, `jobs -p` list background PIDs - **Conditional Execution**: `cmd1 && cmd2` run cmd2 only if cmd1 succeeds, `cmd1 || cmd2` run cmd2 if cmd1 fails - **Brace Expansion**: `touch file{1..10}.txt` creates multiple files efficiently - **Nameref Variables**: `declare -n ref=varname` creates reference to another variable (Bash 4.3+) - **Improved Error Trapping**: `set -Eeuo pipefail; shopt -s inherit_errexit` for comprehensive error handling - **Parallel Execution**: `xargs -P $(nproc) -n 1 command` for parallel processing with CPU core count - **Structured Output**: `jq -n --arg key "$value" '{key: $key}'` for JSON generation - **Performance Profiling**: Use `time -v` for detailed resource usage or `TIMEFORMAT` for custom timing ## References & Further Reading ### Style Guides & Best Practices - [Google Shell Style Guide](https://google.github.io/styleguide/shellguide.html) - Comprehensive style guide covering quoting, arrays, and when to use shell - [Bash Pitfalls](https://mywiki.wooledge.org/BashPitfalls) - Catalog of common Bash mistakes and how to avoid them - [Bash Hackers Wiki](https://wiki.bash-hackers.org/) - Comprehensive Bash documentation and advanced techniques - [Defensive BASH Programming](https://www.kfirlavi.com/blog/2012/11/14/defensive-bash-programming/) - Modern defensive programming patterns ### Tools & Frameworks - [ShellCheck](https://github.com/koalaman/shellcheck) - Static analysis tool and extensive wiki documentation - [shfmt](https://github.com/mvdan/sh) - Shell script formatter with detailed flag documentation - [bats-core](https://github.com/bats-core/bats-core) - Maintained Bash testing framework - [shellspec](https://github.com/shellspec/shellspec) - BDD-style testing framework for shell scripts - [bashly](https://bashly.dannyb.co/) - Modern Bash CLI framework generator - [shdoc](https://github.com/reconquest/shdoc) - Documentation generator for shell scripts ### Security & Advanced Topics - [Bash Security Best Practices](https://github.com/carlospolop/PEASS-ng) - Security-focused shell script patterns - [Awesome Bash](https://github.com/awesome-lists/awesome-bash) - Curated list of Bash resources and tools - [Pure Bash Bible](https://github.com/dylanaraps/pure-bash-bible) - Collection of pure bash alternatives to external commands