shell-script-validationlisted

## Input - Shell script path or directory (optional): defaults to workspace root - Validation script (required): `scripts/validate.sh` - Canonical flags (required): `-v -f -d` unless opted out below - `--check-function-docs` (optional): omit only when targets intentionally skip Google function header sections ## Output Specification Return structured Markdown in accordance with [references/common-output-format.md](references/common-output-format.md). That file is the source of truth for the output contract. Structured results for bash -n and shellcheck (syntax and lint only). With `--check-function-docs`, also reports [Google Shell Style Guide](https://google.github.io/styleguide/shellguide.html#s4.2-function-comments) function header sections. ## Execution Scope - **Always use `scripts/validate.sh`** for comprehensive validation. Do not run individual commands. - Script runs checks in fixed order. - Individual commands are for debugging only (see [references/common-individual-commands.md](references/common-individual-commands.md)). - **Bats output:** By default only failing tests and the summary line are printed. Use `-v` for the full pass/fail listing. ### USE FOR: - run shell script syntax and lint validation before merge - reproduce CI failures for shell scripts - validate a specific script path during iterative fixes - normalize function doc section order when this skill ships `scripts/fix_function_doc_order.sh` ### DO NOT USE FOR: - perform architecture/design