validate

Validate

Let: χ := quality check (name, command from {commands.*}, timeout, result) σ := {✅ pass (exit 0), ❌ FAIL (exit ≠0), ⚠️ warn (exit 0 + warnings), ⏭ skip (¬in scope)}

Run all χ sequentially → single structured pass/fail report. ¬stop on first failure — run all for complete picture.

Pipeline

Step	ID	Required	Notes
1	scope	✓	—
2	run-checks	✓	continue-on-failure
3	report	✓	—
4	failure-details	—	∃ failures
5	verdict	✓	—

Usage

/validate              → Run all checks
/validate --quick      → Lint + typecheck only (fastest)
/validate --full       → All checks including license and coverage
/validate --affected   → Only check files changed vs main

Instructions

1. Scope

Flag	χ set
(none)	lint, typecheck, test, env, i18n
--quick	lint, typecheck
--full	lint, typecheck, test, test:coverage, env, i18n, license
--affected	lint (affected), typecheck:affected, test:affected

2. Run χ Sequentially

∀ χ ∈ scope: run command, capture stdout+stderr + exit code. Record: name, σ, duration, error summary (first 5 lines if failed).

¬raw runner — always use {commands.*} from stack.yml. Command ¬defined → σ := ⏭ skip.

χ	Command	Timeout
Lint	{commands.lint}	60s
Typecheck	{commands.typecheck}	120s
Typecheck (affected)	{package_manager} run typecheck:affected	120s
Test	{commands.test}	180s
Test (affected)	{package_manager} run test:affected	180s
Test coverage	{package_manager} run test:coverage	300s
Env check	{package_manager} run env:check	10s
i18n	{package_manager} run i18n:check	30s
License	{package_manager} run license:check	30s

3. Report

Validate Report
═══════════════

  Check          │ Status │ Duration │ Notes
  Lint           │ ✅ pass │ 2.1s     │ —
  Typecheck      │ ✅ pass │ 8.3s     │ —
  Test           │ ❌ FAIL │ 12.4s    │ 2 failed, 48 passed
  Env check      │ ✅ pass │ 0.3s     │ —
  i18n           │ ⚠️ warn │ 1.1s     │ 3 missing keys in fr.json
  ─────────────────────────────────────────────
  Result: FAIL (4/5 passed, 1 failed)
  Total time: 24.2s

4. Failure Details

∃ χ ∧ σ = ❌ → append failures. First 10 error lines per failing χ.

Failures
────────
Test:
  FAIL src/auth/login.test.ts > should validate token
    AssertionError: expected undefined to be defined
  FAIL src/api/health.test.ts > should return 200
    Error: ECONNREFUSED

5. Verdict

• ∀ χ pass → All checks passed. Safe to push.
• ∃ χ fail → {N} check(s) failed. Fix before pushing.
• --quick ∧ ∀ pass → Quick checks passed. Run /validate for full check.

Edge Cases

Scenario	Behavior
Command not found	σ := ⚠️ warn, "command not available"
Command times out	σ := ❌ FAIL, "timed out after Xs"
¬test files found	σ := ⏭ skip
Docker ¬running (env/db)	σ := ⚠️ warn, ¬fail
Running in worktree	No special handling needed

Safety Rules

1. Read-only — ¬modify files
2. ¬auto-fix — report issues, user decides
3. Run ALL χ — ¬short-circuit on first failure
4. {commands.*} — always use commands from stack.yml, never raw runner (Bun runner ≠ Vitest)

Chain Position

• Phase: Verify
• Predecessor: /ci-watch
• Successor: /code-review
• Class: adv (continuous flow, no gate)

Task Integration

• /dev owns the dev-pipeline task lifecycle externally
• This skill does NOT update its own dev-pipeline task
• Sub-tasks created: none

Exit

• All pass via /dev: return control silently. ¬write summary. ¬ask user. ¬announce /code-review. /dev re-scans and advances.
• All pass standalone: print verdict block + Next: /code-review. Stop.
• Failure: return error. /dev presents Retry | Skip | Abort.

$ARGUMENTS