Skip to content
Skills Library
Programming · Building & coding

bash-robustness

/bash-robustness

Write bash that fails loudly, quotes correctly, cleans up after itself, and passes shellcheck. Use when writing shell scripts that automation or other people will depend on.

Repository
AI-SKILLS ↗
Licence
MIT
Last repository change
05.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Write bash that fails loudly, quotes correctly, cleans up after itself, and passes shellcheck. Use when writing shell scripts that automation or other people will depend on.

Original author description

Write bash that fails loudly, quotes correctly, cleans up after itself, and passes shellcheck. Use when writing shell scripts that automation or other people will depend on.

How it works

  1. Method
  2. Boundaries
Original SKILL.md headings · 62 lines, 450 words
SKILL.md preview
---
name: bash-robustness
description: Write bash that fails loudly, quotes correctly, cleans up after itself, and passes shellcheck. Use when writing shell scripts that automation or other people will depend on.
---

# Bash robustness

Bash's defaults are optimized for interactive forgiveness, not script
correctness: errors continue, unset variables expand to nothing, and
words split themselves. A robust script overrides all three and proves
itself with shellcheck.

## Method

1. **Open with the strict preamble, knowing its limits.**
   `set -euo pipefail` (exit on error, unset-is-error, pipeline
   fails on any stage). Know the honest caveats: `-e` is disabled
   inside `if` conditions and `&&`/`||` chains, and command
   substitution in an assignment (`local x=$(cmd)`) masks failure:
   split declaration and assignment. Where a command may legitimately
   fail, say so: `cmd || true`.
2. **Quote every expansion, always.** `"$var"`, `"$(cmd)"`, `"$@"`
   for argument passthrough: unquoted expansions word-split and
   glob, which is the root of most "works until a space or `*` shows
   up" bugs. Filenames from the world get `--` guards
   (`rm -- "$file"`) and `find -print0 | xargs -0` for iteration.
3. **Clean up with trap, not hope.** Temp files via `mktemp`,
   removed in `trap 'rm -rf "$tmpdir"' EXIT`; the trap runs on
   error and Ctrl-C too, which is the point. Multi-resource scripts
   compose cleanup functions; a script that leaves debris on
   failure is a slow disk-full incident (see graceful-shutdown's
   ethic at script scale).
4. **Fail with context, log to stderr.** `die() { echo "error:
   $*" >&2; exit 1; }` and use it with specifics ("config $f not
   readable"); progress messages to stderr so stdout stays clean
   for data (the python-cli-tools stream contract, shell edition).
   Check preconditions early: required commands
   (`command -v jq >/dev/null || die ...`), required variables,
   expected file existence (see guard-clauses).
5. **Run shellcheck as a gate, not a suggestion.** In CI and
   pre-commit (see git-hooks-automation); fix or explicitly
   directive-suppress every finding with a reason. Shellcheck
   catches the quoting, `-e`, and subshell traps that reviews miss;
   a script that cannot pass it is not done. Format with shfmt for
   diff stability (see code-formatting).
6. **Know when to leave bash.** Past ~100 lines, needing real data
   structures, JSON manipulation beyond one `jq`, error handling
   with context, or unit tests: switch to Python (see
   python-cli-tools) or another real language. Bash excels at
   orchestrating processes and files; it punishes application
   logic (see shell-portability for the dialect question).

## Boundaries

- `set -e` is a tripwire, not error handling; money-path scripts
  (deploys, data mutation) check each critical step explicitly and
  report what succeeded before the failure (see script-idempotency
  for rerun safety).
- Parsing `ls`, HTML, or human-formatted output is fragile by
  construction; use the tool's machine format (`--json`, `-0`,
  `--porcelain`) or a real parser (see text-processing).
- Concurrency in bash (background jobs, `wait`, flock) is
  workable for simple fan-out but has no supervision story;
  parallel pipelines belong in an orchestrator or a language with
  one (see background-jobs).

Versions

The database has no other skills named bash-robustness.

Database snapshot: 13.11.2026 · package version 68479af6ea38 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100shell
    Use when writing Bash scripts or command-line automation. Covers strict mode, safe quoting, argument parsing, trap-based cleanup, portability, and ShellCheck-clean scripts. Trigger on "write a bash script to", "shellcheck is complaining", "my script breaks on filenames with…
  • 100bash-expert
    Expert Bash help for writing, debugging, and optimizing safe, portable shell one-liners and scripts on macOS/Linux. Use when users ask for Bash or POSIX sh commands, script reviews, ShellCheck fixes, quoting/pipeline issues, process/file automation, or converting requirements into shell scripts.
  • 100linux-bash-scripting
    Defensive Bash scripting for Linux: safe foundations, argument parsing, production patterns, ShellCheck compliance. Use when writing bash scripts, shell scripts, cron jobs, or CLI tools in bash.
  • 100linux-bash-scripting
    Defensive Bash scripting for Linux: safe foundations, argument parsing, production patterns, ShellCheck compliance. Use when writing "bash script", "shell script", "linux automation", "system script", "cron job", "deployment script", "CLI tool in bash", or "automate with bash".
  • 100shell-script-validation
    Validate shell scripts with bash -n and shellcheck for syntax safety and maintainability checks. Does not enforce Bats suite pairing (TEST-00) — companion stem `bats` covers pairing rules. Use when committing script changes, running CI validation, or debugging shellcheck findings in PRs.
  • 90shell-scripts
    Use when writing or reviewing Bash scripts and shell snippets, especially for shebang selection, quoting, parameter expansion ("${VAR}" style), test expressions (`[ ]` vs `[[ ]]`), ShellCheck-guided fixes, and portability decisions across POSIX sh, Bash, and zsh compatibility targets.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.