What problem does it solve? After deploying to production, merging a risky PR, or upgrading dependencies, teams often lack immediate visibility into whether the release introduced regressions. This Skill continuously watches a deployed URL and alerts you the moment something breaks. ## Core Features & Use Cases - Multi-Signal Monitoring: Checks HTTP status, new console errors, network failures, Core Web Vitals (LCP/CLS/INP), key page content, and API endpoint health against baselines. - Flexible Watch Modes: Run a single quick check, a sustained watch at a set interval for a defined duration, or a diff comparison between staging and production. - Tiered Alerting: Classifies findings as critical, warning, or info, with desktop notifications, optional Slack/Discord webhooks, and a persistent log file. - Use Case: After pushing a release, run a sustained watch on your production URL every 5 minutes for 2 hours to catch regressions during the launch window before users report them. ## Quick Start Ask the AI to run canary-watch against your deployed URL, for example to monitor https://myapp.com every 5 minutes for 2 hours and report any regressions.