ia-linux-bash-scripting

Generate Linux Bash scripts compliant with ShellCheck and shfmt.

30|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/iliaal/whetstone --skill ia-linux-bash-scripting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ia-linux-bash-scripting
Source: https://github.com/iliaal/whetstone/tree/main/plugins/whetstone/skills/ia-linux-bash-scripting
Command: npx skills add https://github.com/iliaal/whetstone --skill ia-linux-bash-scripting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents fragile, error-prone Bash scripts by enforcing defensive defaults, strict quoting, robust argument parsing, and ShellCheck-friendly production patterns.

Core Features & Use Cases

  • ShellCheck- and shfmt-driven correctness: Produces scripts designed to pass shellcheck --enable=all and shfmt -d with zero warnings.
  • Production-safe Bash patterns: Includes safe temp handling, traps, idempotency helpers, atomic writes, retries with backoff, locking, and predictable logging.
  • Real-world scripting tasks: Fits use cases like cron jobs, CLI tools, deployment helpers, and backup/rotation automation on Linux.

Quick Start

Ask the AI to generate a Linux Bash 4.4+ script that uses set -Eeuo pipefail, strict quoting, argument parsing with helpful --help, and includes a final verification checklist to ensure it runs clean under ShellCheck and shfmt.

Frequently Asked Questions about ia-linux-bash-scripting

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

FAQPage Schema
How do I write Bash scripts that pass ShellCheck warnings?

Bash scripts pass ShellCheck by using strict settings like set -Eeuo pipefail, safe quoting, reliable argument parsing, and trap-based cleanup to ensure verifiable correctness and prevent silent failures.

What is the best way to write safe cron jobs in Linux Bash?

Safe Linux Bash cron jobs use defensive scripting patterns including atomic writes, retries with backoff, locking, predictable logging, and trap-based cleanup to prevent error-prone automation tasks.

How do I add reliable argument parsing to a Bash CLI tool?

Reliable argument parsing in Bash CLI tools requires strict quoting, safe variable expansion, and helpful --help generation, ensuring inputs are handled safely without triggering ShellCheck issues.

Does this defensive Bash scripting approach work with shfmt formatting?

Defensive Bash scripting produces scripts designed to pass shfmt -d formatting checks with zero warnings, ensuring production-safe patterns remain compliant alongside shellcheck --enable=all verification.

Why do my Bash scripts fail silently in production automation?

Bash scripts fail silently when lacking strict settings like set -Eeuo pipefail and trap-based cleanup; defensive scripting enforces reliable error handling and predictable logging to prevent this.