shell-scripts

Formatting and linting shell scripts before committing involves applying shfmt for code formatting and shellcheck for linting, then verifying executability. This workflow ensures all *.sh files in the scripts/ directory follow best practices and are safe to execute.

Enforcing shell script quality involves integrating automated formatting with shfmt, lint checks with shellcheck, and executability verification into your development workflow. This approach streamlines shell-script development and ensures safety when modifying scripts in the scripts/ directory.

Yes, shfmt and shellcheck are required. The skill relies on these external tools to perform formatting and linting, and it requires a shell environment with execute permissions to validate and format your *.sh files properly.

Yes, this validation workflow applies to any repository containing a scripts/ directory with *.sh files. It supports editing, validating, and self-reviewing shell scripts before commits as long as a shell environment with execute permissions is available.

A shell script self-review checklist includes formatting with shfmt, linting with shellcheck, verifying executability, and confirming all *.sh files follow best practices. These validation steps ensure consistency and safety before committing changes.

Shell script executability checks fail when the shell environment lacks proper execute permissions. The validation workflow requires a shell environment with execute permissions to verify that all *.sh files in the scripts/ directory can be safely executed.