
Bash Script Helper
- 37 installs
- 16 repo stars
- Updated November 20, 2025
- jackspace/claudeskillz
Applies bash scripting best practices - strict mode, quoting, getopts parsing, traps, and shellcheck - when writing or debugging shell scripts.
About
A helper skill with bash scripting conventions for writing and debugging shell scripts safely. Developers use it to follow strict-mode, quoting, error-handling, and input-validation best practices.
- Strict mode (set -euo), quoting, and trap-based cleanup
- getopts parsing, arrays, and shellcheck static analysis
Bash Script Helper by the numbers
- 37 all-time installs (skills.sh)
- Ranked #336 of 550 CLI & Terminal skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jackspace/claudeskillz --skill bash-script-helperAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 37 |
|---|---|
| repo stars | ★ 16 |
| Last updated | November 20, 2025 |
| Repository | jackspace/claudeskillz ↗ |
What it does
Applies bash scripting best practices - strict mode, quoting, getopts parsing, traps, and shellcheck - when writing or debugging shell scripts.
Files
Bash-script-helper
Instructions
When writing or debugging bash scripts:
- Always use #!/bin/bash shebang
- Set -e (exit on error), -u (error on undefined var)
- Use [[ ]] instead of [ ] for tests
- Quote variables: "$variable" not $variable
- Use $() instead of backticks
- Check command exit codes: $?
- Use trap for cleanup
- Provide meaningful error messages
- Validate input parameters
- Argument parsing with getopts
- Reading files line by line
- Function definitions and calls
- Arrays and associative arrays
- Use set -x for trace mode
- shellcheck for static analysis
- Use echo/printf for debugging output
- Avoid eval
- Sanitize user input
- Use mktemp for temporary files
- Set proper file permissions
Examples
Add examples of how to use this skill here.
Notes
- This skill was auto-generated
- Edit this file to customize behavior
{
"sections": {
"Notes": "- This skill was auto-generated\n- Edit this file to customize behavior",
"Instructions": "When writing or debugging bash scripts:\n- Always use #!/bin/bash shebang\n- Set -e (exit on error), -u (error on undefined var)\n- Use [[ ]] instead of [ ] for tests\n- Quote variables: \"$variable\" not $variable\n- Use $() instead of backticks\n- Check command exit codes: $?\n- Use trap for cleanup\n- Provide meaningful error messages\n- Validate input parameters\n- Argument parsing with getopts\n- Reading files line by line\n- Function definitions and calls\n- Arrays and associative arrays\n- Use set -x for trace mode\n- shellcheck for static analysis\n- Use echo/printf for debugging output\n- Avoid eval\n- Sanitize user input\n- Use mktemp for temporary files\n- Set proper file permissions",
"Examples": "Add examples of how to use this skill here."
},
"id": "bash-script-helper",
"name": "bash-script-helper",
"description": "Expert helper for bash scripting, debugging, and best practices"
}---
name: bash-script-helper
description: Expert helper for bash scripting, debugging, and best practices
---
# Bash-script-helper
## Instructions
When writing or debugging bash scripts:
- Always use #!/bin/bash shebang
- Set -e (exit on error), -u (error on undefined var)
- Use [[ ]] instead of [ ] for tests
- Quote variables: "$variable" not $variable
- Use $() instead of backticks
- Check command exit codes: $?
- Use trap for cleanup
- Provide meaningful error messages
- Validate input parameters
- Argument parsing with getopts
- Reading files line by line
- Function definitions and calls
- Arrays and associative arrays
- Use set -x for trace mode
- shellcheck for static analysis
- Use echo/printf for debugging output
- Avoid eval
- Sanitize user input
- Use mktemp for temporary files
- Set proper file permissions
## Examples
Add examples of how to use this skill here.
## Notes
- This skill was auto-generated
- Edit this file to customize behavior