What problem does it solve? Deploys that pass CI can still break in production due to missing environment variables, stale CDN caches, or slow migrations. This Skill watches your live app in the critical first minutes after a deploy, catching regressions before users report them. ## Core Features & Use Cases - Baseline Capture: Take screenshots, console error counts, and load times before deploying, then compare post-deploy state against them. - Continuous Monitoring Loop: Check pages every 60 seconds for a configurable duration (1-30 minutes), alerting only on changes that persist across consecutive checks. - Severity-Based Alerts: Classify issues as CRITICAL (page load failure), HIGH (new console errors), MEDIUM (2x performance regression), or LOW (broken links), each with screenshot evidence. - Use Case: After shipping a new release, run the canary against your production URL for 10 minutes. It auto-discovers your main navigation pages, watches them, and produces a health report with a HEALTHY, DEGRADED, or BROKEN verdict. ## Quick Start Ask the assistant to run /canary against your production URL to monitor the deploy for 10 minutes and report any console errors or performance regressions.
