Validate
Overview
Run the tightest available verification loop for current changes, repeat as needed, and report the signal.
Workflow
- •Define "working" for this change (feature path, bug repro, or contract).
- •Choose the smallest scope; prefer local execution.
- •Run available loops in ascending cost: formatter -> lint/typecheck -> build -> targeted tests -> broader tests.
- •If a loop fails or is unavailable, capture the error, propose the smallest fix or ask for the exact command, then re-run the same loop.
- •Escalate only if confidence is still weak after the tighter loop.
Guardrails
- •Do not claim done without at least one real signal.
- •If no validation command exists, add the smallest new signal (focused test or log) or ask for the command.
- •Record what ran and what changed since the last run.
Output
- •Commands run and results.
- •Remaining gaps or next loop to run.