What problem does it solve? Deploys that pass CI can still break in production through missing environment variables, stale CDN caches, or slow migrations. This Skill watches the live app in the first minutes after a deploy and catches regressions before users report them. ## Core Features & Use Cases - Baseline Capture: Takes pre-deploy screenshots, console error counts, and load times per page, then compares post-deploy state against them. - Continuous Monitoring Loop: Checks each monitored page every 60 seconds for a configurable duration (1-30 minutes), alerting only on changes that persist across consecutive checks. - Severity-Based Alerts: Classifies findings as CRITICAL (page load failure), HIGH (new console errors), MEDIUM (2x load time regression), or LOW (new broken links), each backed by a screenshot. - Use Case: After shipping a release, run the canary against your production URL for 10 minutes. It auto-discovers top navigation pages, watches them, and produces a health report with a HEALTHY, DEGRADED, or BROKEN verdict. ## Quick Start Ask the assistant to run the canary skill against your production URL for ten minutes after your next deploy and alert you if any page regresses.
