Quality Gate Orchestrator

Agents often remember to run checks at the end, when it is easiest to miss a failed or skipped gate. Use this skill to track required validation throughout the task.

When to Invoke

• A task has multiple test, lint, build, review, or migration checks
• The user asks for tests-first, verification-first, or completion gates
• Work spans sessions and validation state must survive handoff
• The agent is about to declare completion

Gate Model

Each gate has:

• name - stable identifier such as lint, unit-tests, or migration-dry-run
• command - command to run, if applicable
• required - required gates must pass or be waived before completion
• last_status - pending, pass, fail, or waived