Use when you just corrected an agent or fixed the same failure class twice, or when a change removes a rule, guard, or check.
Use when asked to act as orchestrator, orchestrate with worktrees, run a fleet of parallel subagents on multi-track work, or build and manage many PRs in parallel.
Use when opening a pull request, changing its body, title, or draft state, triaging review comments, writing an issue, or deciding who merges.
Use when asked to rubber duck a change, get a second opinion, or run an independent cross-model review of code changes.
Use when about to report a zero or absent reading, an alarming finding, a success claim, or stillness from a probe or status read, so the reading is evidence-bearing and controlled first.
Use when pushing commits to a remote with CI, merging a PR, or when asked whether a pipeline passed, so every push and merge gets a background watcher.
Use when creating, removing, or handing over git worktrees, or deleting their branches, or when several actors share one repository through worktrees.
Replace with a short trigger stating when the skill should fire, starting with "Use when ...".