mcpField
B
bash-defensive-patterns

bash-defensive-patterns

github.com/sickn33Development48.7k321 installsUpdated 1d ago
Repository

About bash-defensive-patterns

A skill for writing reliable Bash scripts with defensive programming, error handling, and safety practices. It is intended for production automation, CI/CD, and system administration scripts that must handle edge cases.

Key features

  1. 01Strict mode and safe defaults
  2. 02Input validation and safe quoting
  3. 03Logging and error traps
  4. 04Basic tests and file safety
  5. 05Destructive-command safeguards

Use cases

  1. 01Writing production automation scripts
  2. 02Building CI/CD pipeline scripts
  3. 03Creating system administration utilities
  4. 04Developing safer deployment automation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill bash-defensive-patterns

After installing, type/bash-defensive-patternsin Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project README

Bash Defensive Patterns

Comprehensive guidance for writing production-ready Bash scripts using defensive programming techniques, error handling, and safety best practices to prevent common pitfalls and ensure reliability.

Use this skill when

  • Writing production automation scripts
  • Building CI/CD pipeline scripts
  • Creating system administration utilities
  • Developing error-resilient deployment automation
  • Writing scripts that must handle edge cases safely
  • Building maintainable shell script libraries
  • Implementing comprehensive logging and monitoring
  • Creating scripts that must work across different platforms

Do not use this skill when

  • You need a single ad-hoc shell command, not a script
  • The target environment requires strict POSIX sh only
  • The task is unrelated to shell scripting or automation

Instructions

  1. Confirm the target shell, OS, and execution environment.
  2. Enable strict mode and safe defaults from the start.
  3. Validate inputs, quote variables, and handle files safely.
  4. Add logging, error traps, and basic tests.

Safety

  • Avoid destructive commands without confirmation or dry-run flags.
  • Do not run scripts as root unless strictly required.

Refer to resources/implementation-playbook.md for detailed patterns, checklists, and templates.

Resources

  • resources/implementation-playbook.md for detailed patterns, checklists, and templates.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported