Use before opening a pull request and before waiting on CI ("is CI green yet", "merge when green"). Checks queue admission, then polls the CI status API, falling back to gh.
Use to stand up verification scaffolding for a NEW or not-yet-built piece (greenfield repo or component) so it is traceable from commit one ("bootstrap this", "set this up properly from the start").
Use at the end of substantive work or before compaction to distill durable knowledge into the working-context checkpoint and memory ("remember this", "capture what we learned"). Also the monthly skill-usage measurement.
Use before a claim is reported or written, such as findings, audit results, PR or issue text, "0 found", "all green", "because", "verify this", an AI review used as evidence, or a README, badge or doc asserting what the system proves.
Use BEFORE EVERY Agent (Task) call to choose `model:`, and when a delegated tier fails the same check twice. Mechanical work with an exact check goes to haiku.
Use when an unattended agent hits a blocker, a fork it would ask about, something shipped or the end of a session that the owner must know about ("notify me", "ask me later"). Posts a notice and does not wait.
Use to check that checks and evidence can fail and are about the right system ("audit our gates", "can CI actually fail", vacuous or skipped required checks, or an emulator, staging or self-test result filed as "on-target" or "in production" evidence).
Use to run an incremental bug/feature hunt over a repo's issue tracker, handling only what is NEW since the last pass ("hunt the issues", "loop through the issues", a standing loop).