skills.rest
alexjcm
alexjcmCOMMUNITY
Explore all skills by this author →
Website𝕏@alexjhcmGitHub

safe-bash-scripting

Write portable Bash 3.2 scripts with strict quoting and error handling.

Updated Mar 12, 2026
Search Tags:#bash#scripting#best-practices#error-handling#portability#defensive-programming
One-click install
npx skills add https://github.com/alexjcm/agent-skillset --skill safe-bash-scripting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: safe-bash-scripting
Source: https://github.com/alexjcm/agent-skillset/tree/main/skills/tools/safe-bash-scripting
Command: npx skills add https://github.com/alexjcm/agent-skillset --skill safe-bash-scripting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Bash scripting standard provides portable, safe, and maintainable guidelines to ensure scripts run reliably across macOS (Bash 3.2) and Linux, with consistent structures and safety patterns.

Core Features & Use Cases

  • Shebang and strict options: enforce #!/usr/bin/env bash and set -euo pipefail for robust behavior.
  • Portability and compatibility: avoid Bash 4+ features, rely on portable constructs and referencing the provided best-practices.
  • Defensive programming: quoting, input validation, safe file operations, and trap-based cleanup to improve reliability in automation tasks.
  • Use cases include local automation, CI tooling, build scripts, and deployment helpers requiring predictable shell behavior.

Quick Start

Start new Bash scripts by applying the Safe Bash standards: begin with a POSIX-friendly shebang and set -euo pipefail, avoid Bash 4+ features, quote all variables, and reference the provided templates and references.

Frequently Asked Questions about safe-bash-scripting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write Bash scripts that run reliably on both macOS and Linux?▼

Portable Bash scripts for macOS and Linux require a POSIX-friendly shebang like #!/usr/bin/env bash, strict options such as set -euo pipefail, and avoidance of Bash 4+ features to ensure Bash 3.2 compatibility.

What is the best way to handle errors and cleanup in Bash automation scripts?▼

Error handling in Bash automation scripts is best managed through defensive programming, utilizing strict quoting, input validation, and trap-based cleanup to safely handle file operations and improve reliability.

Can I use associative arrays in Bash scripts that need to support macOS?▼

Associative arrays are unavailable for Bash scripts supporting macOS. You must avoid Bash 4+ features and rely on portable constructs to maintain Bash 3.2 compatibility across operating systems.

How do I safely delete files and prevent script failure during local automation?▼

Safely deleting files and preventing script failure during local automation requires defensive programming standards including strict quoting, input validation, safe file operations, and trap-based cleanup mechanisms.

Why does my Bash script fail silently when a command returns an error in CI tooling?▼

Bash scripts fail silently on command errors when strict options are unset. Applying set -euo pipefail enforces robust behavior by immediately exiting on errors and catching pipe failures in CI tooling.

Related Skills

Explore More Software Engineering Skills→
tjmaynestjmaynes
3

bash-script-generator

Generate Bash 3.2-compatible scripts with set -euo pipefail and check_requirements guardrails.

Community
Intermediate
KrismithReddy12KrismithReddy12

land-and-deploy

Merge pull requests, trigger CI/CD pipelines, and validate production health.

Community
Advanced
thimsluggathimslugga

shell-script

Lint and format Bash scripts with ShellCheck and shfmt.

Community
Intermediate
LuisSambranoLuisSambrano
7

posix-pro

Write strict POSIX sh scripts for portability across Unix-like systems.

Community
Advanced