preflight-validator
On-demand wrapper over scripts/preflight/run-all.sh. Runs Tier 1 bash linters against a file, command, or arbitrary content. Returns 0 pass / 1 warn / 2 fail. Used by /aura-frog:preflight check and contributors authoring custom hooks.
What this skill does
> **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 + system files (`/etc/passwd` etc.) + credential dirs |
| `check-command-allowlist.sh` | Hard-block destructive (`rm -rf /`, `mkfs`, fork bombs); warn on risky (`git push --force`, `DROP TABLE`) |
| `check-secret-patterns.sh` | High-confidence credential patterns (AWS, GitHub, OpenAI, JWT, private keys) |
`run-all.sh` orchestrates and returns the **highest** exit code from any linter.
## Exit codes (per spec §20.2)
```toon
exit_codes[3]{code,meaning,downstream_action}:
0,pass,"continue silently"
1,warn,"emit warning, allow"
2,fail,"BLOCK tool call (PreToolUse hook returns 2 → claude-code rejects the tool)"
```
## Invocation patterns
- **Auto** — hook on PreToolUse fires this for every tool call
- **Manual** — `/aura-frog:preflight check` runs run-all.sh against current tool context
- **CI** — `bash aura-frog/scripts/preflight/run-all.sh --files <files>` for batch validation
- **Contributor** — invoke individual scripts directly when authoring a new hook
## What this skill does NOT do
- Does NOT run OPA Tier 2 (deferred to v3.7.0-rc.1+; OPA is optional per spec §20.4)
- Does NOT mutate tool inputs/outputs (read-only)
- Does NOT cache results (each call is fresh — fast enough at ~10ms)
- Does NOT fall back when `bash` is unavailable (Linux/macOS required)
## Tie-Ins
- **Spec:** §9.7, §20 (pre-flight)
- **Script:** `aura-frog/scripts/preflight/run-all.sh` — implementation
- **Hook:** `hooks/pre-flight-validate.cjs` — primary auto-trigger
- **Command:** `/aura-frog:preflight` — user-facing entry
- **Rule:** `rules/workflow/preflight-policies.md` — when, what, bypass policy
- **Future (rc.1):** `aura-frog/scripts/preflight/install-opa.sh` for Tier 2 OPA policies (optional)
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.