What problem does it solve?
Deploying code to production or staging often introduces undetected regressions like broken functionality, performance drops, or API failures that impact users before teams are aware. This Skill automates post-deployment monitoring to catch these issues immediately after a release, reducing mean time to detection and preventing user-facing outages.
Core Features & Use Cases
- Comprehensive regression checks: Monitors HTTP status, new console errors, network failures, core web vital regressions (LCP/CLS/INP), key content element availability, and critical API health against a baseline.
- Flexible watch modes: Run a single quick health check, sustained monitoring over a custom duration and interval, or diff staging vs production environments to catch environment-specific issues.
- Configurable alerting: Sends desktop notifications, optional Slack/Discord webhook alerts, and logs critical issues when predefined thresholds are crossed, ensuring teams can respond immediately to outages.
Use case: After merging a risky PR that updates a core checkout flow, use this Skill to monitor the production URL for 1 hour to catch any broken payment steps or API latency spikes before customers report them.
Quick Start
Use the canary-watch skill to monitor your production deployment URL for 30 minutes immediately after pushing a new release to catch any regressions.