Bash Defensive Patterns
Comprehensive guidance for writing production-ready Bash scripts using defensive programming techniques, error handling, and safety best practices to prevent common pitfalls and ensure reliability.
Use this skill when
- •Writing production automation scripts
- •Building CI/CD pipeline scripts
- •Creating system administration utilities
- •Developing error-resilient deployment automation
- •Writing scripts that must handle edge cases safely
- •Building maintainable shell script libraries
- •Implementing comprehensive logging and monitoring
- •Creating scripts that must work across different platforms
Do not use this skill when
- •You need a single ad-hoc shell command, not a script
- •The target environment requires strict POSIX sh only
- •The task is unrelated to shell scripting or automation
Instructions
- •Confirm the target shell, OS, and execution environment.
- •Enable strict mode and safe defaults from the start.
- •Validate inputs, quote variables, and handle files safely.
- •Add logging, error traps, and basic tests.
Safety
- •Avoid destructive commands without confirmation or dry-run flags.
- •Do not run scripts as root unless strictly required.
Refer to resources/implementation-playbook.md for detailed patterns, checklists, and templates.
Resources
- •
resources/implementation-playbook.mdfor detailed patterns, checklists, and templates.