validatelisted

# Validation Orchestrator Run all applicable validators against recent code changes. ## Step 1: Determine which validators to run Check what files have changed. Combine committed, staged, and unstaged changes to capture all recent work: ```bash { git diff HEAD~1 HEAD --name-only --diff-filter=ACMRT 2>/dev/null; git diff --cached --name-only --diff-filter=ACMRT 2>/dev/null; git diff --name-only --diff-filter=ACMRT 2>/dev/null; } | sort -u ``` Based on file extensions, select validators: - `.go` files → run `go-effective`, `go-proverbs` - `.py` files → run `python-style` - `.ts` or `.tsx` files → run `typescript-style` - All files → run `security` - All files → run `state-machine` - All files → run `error-handling` ## Step 2: Run validators in parallel Use the Task tool to spawn validators in parallel. For each applicable validator, create a Task with: - subagent_type: "general-purpose" - prompt: Use the Skill tool to invoke the validator. The prompt must explicitly require skill invocation and verbatim JSON output. **Example Task prompt for each validator:** ```text Invoke the `go-effective` skill using the Skill tool (skill: "go-effective"). Return its JSON output verbatim — do not summarize, reformat, or re-implement the validation logic. ``` **Go files changed:** 1. Task: Invoke `go-effective` skill and return JSON output verbatim. 2. Task: Invoke `go-proverbs` skill and return JSON output verbatim. 3. Task: Invoke `security` skill and return JSON output verbatim. 4