watch

Run a manual full sweep to triage Drover environments and verify awaiting-review fixes.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/cosmicdreams/claude-plugins --skill watch-cosmicdreams
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: watch
Source: https://github.com/cosmicdreams/claude-plugins/tree/main/drover/skills/watch
Command: npx skills add https://github.com/cosmicdreams/claude-plugins --skill watch-cosmicdreams

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually triaging all Drover environments and verifying which “awaiting review” tickets were actually fixed when continuous monitoring is insufficient or when onboarding is incomplete.

Core Features & Use Cases

  • One-off full sweep across environments: Runs a triage cycle for every configured enabled environment in parallel, instead of waiting for the umbrella monitor to detect changes.
  • Pre-flight safety checks: Validates Drover configuration, board initialization, and DDEV health (including drush verification) before spawning any triage agents.
  • Verification and ticket lifecycle updates: Checks fingerprints against the current cycle’s observed deltas to reopen ineffective fixes and auto-close repeatedly absent issues.
  • State checkpointing: Merges per-environment results into a consolidated ~/.claude/drover.state.jsonl record for later analysis and continuity.

Quick Start

Run the manual sweep loop by invoking /loop 3m /drover:watch for the project you want to triage right now.

Frequently Asked Questions about watch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manually triage Drover environments when continuous monitoring isn't catching fixes?

Manual triage of Drover environments executes a full sweep across all configured environments in parallel to verify awaiting-review tickets against current cycle fingerprints without waiting for continuous monitoring.

What pre-flight checks are required before running a DDEV drush triage cycle?

Running a DDEV drush triage cycle requires validating Drover configuration, board initialization, and DDEV health including drush verification before spawning any per-environment triage agents.

Can I triage a Drupal project that isn't registered with drover:add-project yet?

Yes, you can triage unregistered Drupal projects by running a manual full sweep, which is specifically designed for projects not yet registered via drover:add-project or for one-off debugging cycles.

How does fingerprint verification update Kanban ticket labels for awaiting-review fixes?

Fingerprint verification checks observed deltas against the current cycle to update ticket labels, reopening ineffective fixes and auto-closing issues that show consecutive absences past threshold limits.

What is the best way to run a one-off Drover triage sweep on demand?

The best way to run a one-off Drover triage sweep on demand is invoking the manual loop command, which spawns per-environment triage agents into an incrementally named team to process enabled environments.

Where does the Drover watch sweep store consolidated triage state for later analysis?

The Drover watch sweep merges per-environment triage results into a consolidated state checkpoint file to maintain continuity and enable later analysis of the verified ticket lifecycle updates.