go-validationlisted

## Input - Go path or directory (required) - Validation script: `scripts/validate.sh` (required, run from the go-validation skill directory) - Optional flags: `--fix`, `--verbose` ## 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 validation results in fixed tool order. ## Execution Scope - **Always use `scripts/validate.sh`** for comprehensive validation. Do not run individual commands. - Individual commands are for debugging only (see [references/common-individual-commands.md](references/common-individual-commands.md)). - **Do not review code design decisions** (use go-review). - **Do not modify source files** except `--fix` formatting. - **Do not create or delete files**. ### USE FOR: - run deterministic Go validation before commit or merge - reproduce CI failures for Go format/lint/test/vulnerability checks - verify coverage threshold and blocking validation status ### DO NOT USE FOR: - perform architecture or design reviews (use `go-review`) - generate new source code as a primary task - validate non-Go projects ## Reference Files Guide - [common-checklist.md](references/common-checklist.md) (always read) - [common-output-format.md](references/common-output-format.md) (always read) - [common-troubleshooting.md](references/common-troubleshooting.md) (read on failure) - [common-individual-commands.md](