shell-script-validation

You can automate shell script validation by running a centralized `validate.sh` workflow that integrates syntax checks, static analysis with shellcheck, formatting with shfmt, and tests with bats. This workflow scans all Bash scripts in your workspace to catch errors before deployment.

To lint and format Bash scripts, you need bash for syntax checking, shellcheck for static analysis, shfmt for formatting verification, bats for unit testing, and jq for processing validation outputs. These dependencies work together within the validation workflow.

Yes, you can automatically fix shell script issues by running the validation workflow with the `-f` flag. Combined with the `-v` flag for verbose output, the workflow uses shfmt and patch to apply formatting fixes and report remaining issues.

Yes, shellcheck and bats are integrated into a single validation workflow. The workflow runs shellcheck for static analysis and security checks while simultaneously executing bats to run unit tests, providing comprehensive feedback for CI pipelines and local debugging.

The best way to check dependencies is using the centralized validation workflow, which includes basic dependency verification alongside syntax checks and static analysis. Running `validate.sh` ensures your Bash scripts are correct, secure, and have their dependencies verified before deployment.

Validation may fail in CI due to formatting issues detected by shfmt or static analysis warnings from shellcheck that local syntax checks miss. The centralized workflow catches style issues, security vulnerabilities, and test gaps that standard bash interpretation does not identify.