shell-discipline

What problem does it solve?

Shell scripts can accidentally cause outages or data loss due to quoting mistakes, unsafe defaults, missing error handling, and destructive commands running with bad or empty variables.

Core Features & Use Cases

• Safety preamble: Enforces set -euo pipefail so failures stop the script, undefined variables don’t silently become empty, and pipeline errors aren’t hidden.
• Variable hygiene: Applies consistent quoting rules, ${var} clarity, and required-variable checks using ${VAR:?message}.
• Destructive-command guardrails: Flags high-risk patterns like rm -rf, recursive chmod/chown, dangerous redirects, and overwriting file operations, then provides safer validation patterns.
• Operational script structure: Recommends cleanup functions with trap ... EXIT, readonly constants, validation before action, and contextual logging.
• Quality control: Integrates ShellCheck into local and CI workflows, treating warnings as actionable failures to reduce real-world bugs.

Quick Start

Use the shell-discipline skill to generate a production-ready bash script by following the required safety preamble, quoting, variable validation, and ShellCheck-first practices for the task you are automating.