← ClaudeAtlas

wait-for-itlisted

Use when the user wants to be told when something happens later, or asks you to monitor or watch something still in progress: CI or a build finishing, PR checks or reviews landing, a deploy or release going out, a feature flag taking traffic, a log line appearing, a metric crossing a threshold. Triggers on "monitor CI", "monitor the PR", "monitor the deploy", "watch it through deploys", "ping me when", "tell me as soon as", "let me know when", "notify me if", "wait for it to finish". Also use when monitoring is the second half of a request ("open the PR and keep an eye on the checks", "ship it, then watch the canary", "retry the job and stay on it"): load this before doing the first step, so a watch gets armed instead of a blocking `gh run watch` or a sleep loop. Also use when a prompt-cron or /loop is polling with no-op ticks. Do NOT use for reading current state once (just read it), for setting up permanent alerting (Datadog monitors, pager rules), or for a watch that must survive the session ending.
technicalpickles/pickled-claude-plugins · ★ 13 · AI & Automation · score 73
Install: claude install-skill technicalpickles/pickled-claude-plugins
# wait-for-it Turn "tell me when X happens" into a shell probe that emits only when X actually happens. ## The failure this exists to prevent A scheduled task or a dynamic `/loop` re-evaluates a **prompt** every tick. A tick where nothing happened still costs a full model turn and still emits a message. Observed: a 26-second Opus turn whose entire output was "No new hits." `Monitor` and `Bash(run_in_background)` cost **zero tokens** while nothing is happening, because they run a command and only your printed lines become notifications. ## Step 1: pick the tool | What the user wants | Use | |---|---| | One notification total, then done | `Bash` with `run_in_background: true`, running `watch-loop.sh --once` | | One per occurrence, indefinite | `Monitor` with `timeout_ms` at the max, re-armed on each expiry | | One per occurrence, until a known time/tick budget runs out | `Monitor`, with `--max-ticks` set from that budget | | One per occurrence, until the target reaches a known terminal state | `Monitor` with `timeout_ms` at the max, re-armed on each expiry, open-ended (no `--once`/`--max-ticks`) — `watch-loop.sh` has no "stop when terminal" flag, so judge completion from the emitted lines and stop the `Monitor` yourself with `TaskStop` | | Must survive the session ending | **Stop.** See "The session ceiling" below. | Ask which, if it is not obvious. "Ping me when the first hits come in" is ambiguous between row 1 and row 2: the user says *first*, which sounds one-shot, b