preflight-validatorlisted

> **AI-consumed reference.** Optimized for Claude to read during execution. > Human-readable explanation: see [docs/architecture/HIERARCHICAL_PLANNING.md](../../../docs/architecture/HIERARCHICAL_PLANNING.md) > or [docs/getting-started/](../../../docs/getting-started/) depending on topic. # Pre-flight Validator **STATUS — v3.7.0-beta.1.** Thin wrapper over `aura-frog/scripts/preflight/run-all.sh`. ## When this skill runs vs. when the hook runs - **`hooks/pre-flight-validate.cjs`** — auto-fires on every PreToolUse for Bash/Edit/Write/Read. Blocks tool call on fail. **You don't have to do anything for this — it's automatic.** - **This skill** — explicit invocation when you want to validate something the hook doesn't see. Examples: validating a markdown file before committing, dry-running a Bash command's safety, batching a directory of plan files through frontmatter validation. ## Behavior 1. Resolve target: file path / Bash command string / stdin content 2. Run `bash aura-frog/scripts/preflight/run-all.sh` with the appropriate flags 3. Surface exit code + stderr to caller ## Tier 1 linters (per spec §20.2) | Script | Checks | |---|---| | `validate-frontmatter.sh` | YAML frontmatter on plan/skill/agent/rule/command markdown | | `validate-tool-input.sh` | Tool input shape — required fields, absolute paths, no-op edits | | `validate-tool-output.sh` | ANSI-escape volume, prompt-injection phrases, JSON-claim sanity | | `check-path-safety.sh` | Reject path traversals + syste