bash-prolisted

## 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